8 posts tagged with "August"

Week 34 (August 20st – August 27th)​

• pull-from-upstream is now supported also without specifying upstream_project_url in the configuration. For such cases, the upstream repository will not be detected and cloned during release syncing. (packit#2398)
• dist-git init command now allows upstream-git-url not to be specified. (packit#2387)
• You can newly tag builds of a package into a sidetag group by using /packit koji-tag comment command. (packit-service#2507)
• Thanks to Cristian Le, epel-10 is now correctly mapped to a centos-stream-10 when running tests. (packit-service#2508)

Week 33 (August 13th – August 19th)​

• Several internal, but also performance improvements were done on our dashboard, thanks to Freya Gustavsson (packit/dashboard#435)!

Week 32 (August 6th – August 12th)​

• Packit now passes PACKIT_TAG_NAME to the Testing Farm run when it's triggered by a release event. Thanks @Frawless. (packit-service#2494)

Week 31 (July 30th – August 5th)​

• It is now possible to run tests for releases. (packit/packit-service#2490)

Week 35 (August 29th – September 4th)​

• Now Packit exposes PACKIT_PACKAGE_NAME, PACKIT_UPSTREAM_PACKAGE_NAME and PACKIT_DOWNSTREAM_PACKAGE_NAME env variables to all the actions. (packit#2061)
• Packit now sets PACKIT_UPSTREAM_REPO and PACKIT_DOWNSTREAM_REPO environment variables for release syncing actions. The variables represent paths where the respective git repositories are cloned (packit-service#2166)
• We have fixed a bug causing issues with displaying some Project views on our dashboard. (packit-service#2165)

Week 34 (August 22nd – August 28th)​

• We have fixed a bug in packit source-git init caused by the changed behaviour in the newer version of rpmbuild. (packit#2048)
• We have fixed an issue in our API endpoint that could cause DoS until manual intervention from our team. (packit-service#2164)
• We have fixed a bug causing broken retriggering of Github checks. (packit-service#2161)
• SRPM build commit statuses, for monorepos projects, are now being correctly updated. (packit-service#2157)
• We have fixed the bug resulting in incorrect reporting for tests when retriggering a build of a different target that was not configured for tests. (packit-service#2144)
• We have fixed an issue that caused retriggers of Testing Farm to fail, if you specified any labels in the comment and had one or more test job definitions without any labels specified. (packit-service#2156)
• Macro definitions and tags gained a new valid attribute. A macro definition/tag is considered valid if it doesn't appear in a false branch of any condition appearing in the spec file. (specfile#276)

Week 32 (August 8th – August 14th)​

• Two new configuration options for filtering when getting latest upstream release tag were introduced: upstream_tag_include and upstream_tag_exclude. They should contain a Python regex that can be used as an argument in re.match. (packit#2030, packit-service#2138)
• Retriggering of pull-from-upstream via a comment will now use the correct configuration file from the default dist-git branch. (packit-service#2140)
• The pull-from-upstream job can now be used with upstream repos that are not hosted on a supported git forge. (packit-service#2137)

• Licenses in Packit specfiles are now confirmed to be SPDX-compatible. (example PR: packit#2026) If you are interested in more details, see a talk from Flock 2023 by Mirek.