Skip to main content

· 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.

· One min read
Maja Massarini

Week 48 (November 26th – December 2nd)​

  • There is a new action/hook, post-modifications, that is executed after all modifications to the spec file are done and in case of syncing release after all remote sources are downloaded and before uploading to lookaside cache. You can use it for example to construct an additional source that depends on the primary source (that may not yet be available in other actions). (packit#2474)
  • We have fixed /packit retest-failed which was retriggering also non failed tests. (packit-service#2665)
  • Packit now includes dashboard links when reporting errors for Koji builds and Bodhi updates. (packit-service#2663)
  • We have improved Koji builds and Bodhi updates errors displaying. (dashboard#497)