Skip to main content

Week 41 in Packit

· 2 min read

Week 41 (October 10th – October 16th)

  • (breaking) Packit no longer accepts packit.json or .packit.json as a configuration file name. (packit#2123)
  • We have implemented several improvements in syncing the release downstream:
    • Packit now updates ACL of its own dist-git forks to allow users and groups with commit rights to the original dist-git repo to push directly to a fork. (packit#2112)
    • Packit now also properly cleans up the branch after syncing the release which should prevent unwanted files (e.g. tarballs) being committed to dist-git. (packit#2125)
    • We have adjusted the way how Packit includes the resolved bugzillas in the commit messages created when syncing the release downstream so that the resolved bugzillas are included in changelog when using %autochangelog. (packit#2126)
  • Packit now reacts to retriggering comments for downstream jobs by commenting on the same issue/PR and providing information about the jobs. (packit-service#2222)
  • We have fixed an issue that prevented you from running the jobs on the due to failing resolution of the upstream/downstream relationship for the cloned project. (packit#2120)
  • Packit now triggers the build for the /packit test comment command if the last build was not successful. (packit-service#2228)

And special thanks to @SpyTec for multiple wonderful dashboard improvements!