Week 2 (January 7th – January 13th)​

• Fixed EVR regex used when parsing changelog entries in the specfile library to not match email addresses with - in them. (contributed by Dan Čermák, specfile#445)

Week 1 (January 2nd – January 6th)​

• We have improved fallback commit status reporting via comments in GitLab. (packit-service#2686)

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)

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.

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)

Week 47 (November 19th – November 25th)​

• Packit now uses the fedora-distro-aliases library to expand Fedora aliases. This is Packit's original code being improved and properly maintained by the Copr team. For further suggestions about aliases, use github.com/rpm-software-management/fedora-distro-aliases. (packit#2470)

Week 46 (November 12th – November 18th)​

• The Packit configuration file now supports a top-level placeholder key, _, which is ignored when parsing the file. This is useful for storing YAML anchors in complex config files, e.g.:

_:
  base-test: &base-test
    job: tests
    fmf_path: .distro
jobs:
  - <<: *base-test
    trigger: pull_request
    manual_trigger: true
  - <<: *internal-test
    trigger: commit
    use_internal_tf: true

(packit#2378)

• You can now define with_opts and without_opts in target-specific configuration of copr_build job to build with --with and --without rpmbuild options. (packit#2463)
• We have made several improvements to our dashboard:
  • The Copr installation instructions have been updated. (dashboard#487)
  • You can now view the number of new findings from OpenScanHub scans. (dashboard#489)
  • Displaying of Copr builds in Testing Farm run views was improved as well. (dashboard#481)

Week 45 (November 5th – November 11th)​

• Packit now provides information about submitted scans via /osh-scans API endpoint. (packit-service#2614)
• We have improved reporting of OpenScanHub results. (packit-service#2622)

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)