Week 44 (October 29th – November 4th)​

• Packit now supports and defaults to fast_forward_merge_into syntax via --dist-git-branches-mapping in dist-git init. (packit#2456)

Week 43 (October 22nd – October 28th)​

• We have added support for retriggering jobs that are configured for commit and release trigger. Retriggering can be done via commit comments on the relevant commit, using the usual comments, such as /packit build or /packit test, but the branch or tag need to be specified like this (without the arguments, we will default to commit trigger for the default branch of the repository):

  /packit build --commit <branch-name>
  

  or

  /packit build --release <tag-name>
  

  (packit-service#2589)

• There is a new method for getting a single commit comment, supporting also retrieval and adding reactions in GitHub. (ogr#865)

• We have improved the feedback for the Open Scan Hub job. You can now see if the scan is in a pending, running, canceled, failed, or successful state. A failed or canceled scan is shown as neutral and does not cause your pull request validation to fail. (packit-service#2543)

Week 42 (October 15th – October 21st)​

• Manual test trigger command (/packit test) now accepts --env option(s) to override environment variables passed to Testing Farm. (packit-service#2583)

Week 41 (October 8th – October 14th)​

• We have fixed an issue that was introduced during the unification of the interface for passing resolved Bugzillas / Jira tickets to the sync-release or bodhi_update jobs. (packit#2442)

Week 40 (October 1st – October 7th)​

• packit validate-config now checks for the existence of the downstream package. (packit#2436)
• Packit now allows building VM images via CLI without any Copr repository specified. (packit#2434)
• We have unified interface of passing resolved bugs (e.g., Bugzillas as of now) to Packit CLI and via comments. Both CLI and comments now use --resolve-bug switch (comments accept comma-separated list of bugs, CLI accepts the switch multiple times (also -b)). (packit#2428 and packit-service#2560)
• packit init now adds working directories that are used in packit prepare-sources into the .gitignore file in the same directory where Packit config resides. (packit#2431)
• Before triggering the non-scratch Koji builds, we now check whether there is not already a build in progress or completed for the same NVR. (packit-service#2559)
• We have improved the error reporting for failed downstream jobs. (packit-service#2544)
• We have fixed an issue that caused inconsistencies with the expected behaviour stated by the documentation when adding duplicitous reactions to GitLab comments. (ogr#861)

Week 39 (September 24th – September 30th)​

• Check for upstream_project_url presence in the configuration when pull_from_upstream job is configured was removed from validate-config, as this is no longer required. (packit#2423)
• We have added a note about retriggering pull_from_upstream job from dist-git pull requests. (packit-service#2542)

Week 38 (September 17th – September 23rd)​

• Packit now allows to configure mock bootstrap feature setup of Copr projects with a new bootstrap configuration option. (packit#2411)

Week 37 (September 10th – September 16th)​

• We have fixed showing of Bodhi updates that are triggered by non-Packit Koji builds on our dashboard. (packit-service#2528)

Week 36 (September 3rd – September 9th)​

• Packit now supports passing custom arguments to various static analyzers through --csmock-args CLI option and csmock_args configuration. (packit#2402)
• When syncing a new release, Packit can now avoid diverging git branches by reusing the commit from one branch when opening pull requests into other branches. (These pull requests can be merged in fast-forward mode.) Use the new syntax for dist_git_branches as in this example to utilise this functionality:

{
  "rawhide": {
    "fast_forward_merge_into": ["f40"]
   },
  "fedora-stable": {}
}

(packit-service#2478)

Week 34 (August 20st – August 27th)​

• pull-from-upstream is now supported also without specifying upstream_project_url in the configuration. For such cases, the upstream repository will not be detected and cloned during release syncing. (packit#2398)
• dist-git init command now allows upstream-git-url not to be specified. (packit#2387)
• You can newly tag builds of a package into a sidetag group by using /packit koji-tag comment command. (packit-service#2507)
• Thanks to Cristian Le, epel-10 is now correctly mapped to a centos-stream-10 when running tests. (packit-service#2508)