-
Notifications
You must be signed in to change notification settings - Fork 51
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add blog post for week 48 Reviewed-by: František Lachman <[email protected]> Reviewed-by: Matej Focko
- Loading branch information
Showing
1 changed file
with
21 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
--- | ||
title: Week 48 in Packit | ||
date: 2023-12-04 | ||
authors: nforro | ||
tags: | ||
- 2023-November | ||
- 2023 | ||
- November | ||
--- | ||
|
||
## Week 48 (November 28th – December 4th) | ||
|
||
- Packit now links the information related to upstream events in PRs opened when syncing a release. | ||
([packit#2173](https://github.com/packit/packit/pull/2173)) | ||
|
||
- When accessing tags or macro definitions by name, specfile library now takes validity into account | ||
when looking for the best match. For example if there are two instances of `Version` tag, | ||
one in the true and one in the false branch of a condition, `Specfile.version` will always access | ||
the one that is in the true branch. | ||
This also applies to Packit when syncing a release and updating value of `Version` tag. | ||
([specfile#328](https://github.com/packit/specfile/pull/328)) |