Week 21 (May 20th – May 26th)
- We have fixed a bug that caused specfile to traceback when section names with conditional macro expansions containing spaces were present in the spec file. (specfile#476)
Week 21 in Packit
· One min read
Week 20 in Packit
· One min read
Week 20 (May 13th – May 19th)
- We have added a support for passing
upstream_package_nameto theupstream_tag_templateoption. (packit#2604)
Week 19 in Packit
· One min read
Week 19 (May 5th – May 13th)
- You can now validate a Packit config passed to the Packit CLI via a path, e.g.,
packit config validate -c /tmp/my-custom-packit-config.yml. (packit#2556) - Packit now runs custom TMT tests as part of CI on dist-git pull requests (documentation). (packit-service#2792)
- We have fixed posting duplicated comments about invalid configurations. (packit-service#2788)
Week 18 in Packit
· One min read
Week 18 (April 29th – May 5th)
Installability check is now being run as part of CI on dist-git pull requests. For more information, please refer to our documentation. (packit-service#2782)
Support for Forgejo pull requests has been added. (ogr#925)
Week 16 in Packit
· One min read
Week 16 (April 16th – April 22nd)
- The
--resultdirargument inbuild_in_mocknow defaults to the current directory ("."), preventing loss of build artifacts when not explicitly set. (packit#2567) tf_extra_paramsshould now be included when submitting the automatic upstream installability check to the Testing Farm. (packit-service#2779)
Week 15 in Packit
· One min read
Week 15 (April 8th – April 14th)
- There is a new
osh_optionsconfig option that allows you to customize OpenScanHub scans. (packit#2570)
Week 14 in Packit
· One min read
Week 14 (April 1st – April 7th)
- When using
fast_forward_merge_into,version_update_maskis now correctly being taken into consideration. (packit#2551) - We have introduced a new
configcommand group for configuration-related commands and moved thevalidate-configcommand under it, resulting in the new command beingpackit config validate. (packit#2559) - It is now possible to retrigger dist-git CI scratch builds with
/packit scratch-build. (packit-service#2770)
Week 13 in Packit
· One min read
Week 13 (March 25th – March 31st)
- We have fixed an issue that could cause subsequent runs
of
propose_downstream/pull_from_upstreamto fail if upstream git repo contains submodules that are manipulated with in actions. (packit-service#2768) - Packit now supports
--base-nvroption when submitting scans to OpenScanHub. The base NVR is pulled in from Koji to perform a differential scan. (packit#2569) - Packit CLI now submits Koji builds in parallel. (packit#2568)
Week 11 in Packit
· One min read
Week 11 (March 11th – March 17th)
- It is now possible to set
use_target_repo_for_fmf_urlconfiguration flag to bypass the default passing of fork URLs for test requests. (packit-service#2752) - Packit as Fedora CI no longer overwrites Koji scratch build statuses on a PR when the same commit is shared between different target branches. (packit-service#2747)
- New aliases for minor versions of EPEL have been added, see the documentation for more details. (fedora-distro-aliases#27)
Week 9 in Packit
· One min read
Week 9 (February 25th – March 3rd)
- (Fedora dist-git CI beta) You can now trigger scratch Koji builds from the dist-git PRs even when the PR is created from the branch on the same repository. (packit-service#2732)