Skip to main content

· One min read
František Lachman

Week 24 (June 11th – June 17th)​

  • We have fixed a bug that caused inconsistency between the promised environment variables (from the docs) and the environment that has been actually provided. Now you should have access to PACKIT_UPSTREAM_REPO and PACKIT_DOWNSTREAM_REPO (in case of propose_downstream and pull_from_upstream jobs), in the post-upstream-clone action. (packit#2327)

· One min read
František Lachman

Week 19 (May 7th – May 13th)​

  • Added a scan-in-osh subcommand in the CLI to perform a scan through OpenScanHub. By default it performs a full scan of the packages and a differential scan can be performed through --base-srpm option. (packit#2301)

· One min read
Nikola Forró

Week 18 (April 30th – May 6th)​

  • Packit will now upload to lookaside cache sources that are not specified by URLs and are present in the dist-git repo during release sync. Additionally, all the actions ran during syncing release will provide the PACKIT_PROJECT_VERSION environment variable. (packit#2297)
  • We have introduced a new status_name_template option that allows you to configure status name for a Packit job. For further details have a look at our docs. This feature is still experimental and at the moment it is not possible to retry such jobs via GitHub Checks' re-run. (packit-service#2402)

· One min read
Laura Barcziová

Week 17 (April 23rd – April 29th)​

  • We have fixed the syncing of ACLs during CentOS Stream release syncing. (packit#2298)
  • koji_build job has a new sidetag_group option that allows to perform a downstream Koji build in a sidetag. A new sidetag will be created for each configured dist_git_branch if it doesn't already exist. This represents the first step towards multi-package Bodhi updates. Stay tuned for further advancements! (packit-service#2409)
  • We have fixed an issue when copr_build job status checks were sometimes wrongly updated with a misleading message after a SRPM build failure. (packit-service#2406)