Skip to main content

· One min read
Nikola Forró

Week 11 (March 11th – March 17th)​

  • It is now possible to set use_target_repo_for_fmf_url configuration 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)

· One min read
Matej Focko

Weeks 3–4 (January 14th – January 27th)​

danger

This is also a breaking release that includes changes from the Packit 1.0.0, we have opened PRs that should help you with migration if you are affected.

For more details please see the following blog post.

  • Added support for detached (open)SUSE style changelogs (specfile#444, contributed by Dan Čermák)

· One min read
Matej Focko

Week 50 (December 10th – December 16th)​

  • We have added a --resultdir option for building in mock via our CLI (packit build in-mock). (packit#2475)

  • For our specfile users, there is a new convenience method Sections.get_or_create() that allows you to manipulate a section without checking if it exists first. If a section doesn't exist, it will be appended to the end. For example, this will work properly even on spec files without %changelog:

    with spec.sections() as sections:
        changelog = sections.get_or_create("changelog")
        changelog[:] = ["%autochangelog"]

    (specfile#441)

  • We have also switched our base images from CentOS 9 Stream to Fedora 41 to allow you using the features from the latest rpm 4.20. (deployment#622)

  • We have unified status names for VM Image builds. (packit-service#2679)

  • We have started building our container images for alternative architectures. (packit-service#2675)

· One min read
František Lachman

Week 49 (December 3rd – December 9th)​

  • It's finally here! The team is planning to release Packit 1.0.0! We want to take this opportunity to clean up long-time deprecated config options and a related code. To not let you alone in this, you can expect a pull request with required changes in case you are affected. More information about this change can be found on a separate page.