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-releaseorbodhi_updatejobs. (packit#2442)
sync-release or bodhi_update jobs. (packit#2442)packit validate-config now checks for the existence of the downstream package. (packit#2436)--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)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)pull_from_upstream job from dist-git pull requests. (packit-service#2542)bootstrap configuration option. (packit#2411)--csmock-args CLI option and csmock_args configuration. (packit#2402)dist_git_branches as in this example to utilise this functionality:{
"rawhide": {
"fast_forward_merge_into": ["f40"]
},
"fedora-stable": {}
}
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)/packit koji-tag comment command. (packit-service#2507)epel-10 is now correctly mapped to a centos-stream-10 when running tests. (packit-service#2508)PACKIT_TAG_NAME to the Testing Farm run when it's triggered by a release event.
Thanks @Frawless.
(packit-service#2494)