Were you annoyed by Packit creating divergent branches in your package's dist-git repository? You'll be happy to know that Packit now supports a new dist_git_branches
syntax that enables fast-forwarding commits between branches.
4 posts tagged with "propose-downstream"
View All TagsCall for volunteers: help to test us the release syncing using staging instance
In the upcoming months, we plan to migrate our service to a new cluster. However, this may affect propose_downstream
and pull_from_upstream
jobs due to the new firewall rules. The problematic aspects could be:
- commands you run in your
actions
during syncing the release involving interactions with external servers - downloading your sources from various hosting services (crates.io, npm, gems, etc.)
To smoothen this transition, we kindly encourage you to enable one of these jobs on our already migrated staging instance. This recommendation is particularly important if you belong to one of the groups affected by the two previous points. This proactive step will help us identify and address any issues promptly.
Handling of Release field in propose_downstream job
We have recently made some fixes to the process of handling the Release
field regarding the %autorelease
macro, so let's take that opportunity to explain how it works.
Downstream automation is here
Finally, it's here. Now, you can do the whole Fedora release with the help of Packit. Let's take a look at how it works on an example of OGR, the Python library we develop.