Week 9 (February 25th – March 3rd)
- (Fedora dist-git CI beta) You can now trigger scratch Koji builds from the dist-git PRs even when the PR is created from the branch on the same repository. (packit-service#2732)
Week 9 in Packit
· One min read
8 posts tagged with "February"
View All TagsWeek 7 in Packit
· One min read
Week 7 (February 11th – February 17th)
- Packit now reloads spec files after all
actionsthat might modify them during release syncing. This adds support for use cases like regenerating the spec file, see rust2rpm example. (packit#2521)
Week 6 in Packit
· One min read
Week 6 (February 4th – February 10th)
- Packit doesn't attempt to upload git-tracked remote sources (for example a GPG keyring) to lookaside cache anymore when syncing release. (packit#2518)
- Dashboard pagination has been changed from infinite loading to page-based. (dashboard#500)
Week 9 in Packit
· One min read
Week 9 (February 27th – March 4th)
- We have fixed the bug about Packit overwriting the final state of the build in case the build start is being processed later than the end of the build. (packit-service#2358)
- We have improved the reporting of configuration errors in GitLab. (packit-service#2357)
GitLabProject.get_file_content()can now correctly handle file paths starting with./. (ogr#844)
Week 8 in Packit
· One min read
Week 8 (February 20th – February 26th)
- Packit now checks the version to propose against the version in specfile and doesn't create downgrade PRs. (packit#2239)
Week 7 in Packit
· One min read
Week 7 (February 13th – February 19th)
- Packit now supports special value
ignorefortriggerin jobs configuration that indicates not to execute the job at all. This can be useful for templates or temporarily disabled jobs. (packit#2234) - We have fixed the caching of data for the usage API endpoint. (packit-service#2350)
- We have fixed an issue that caused loading the same data multiple times on the dashboard within the project views. (packit-service#2349)
- We have also fixed crashing of dashboard's
Usagepage in case of unsuccessful queries. (dashboard#378) - We have fixed parsing of resolved Bugzillas in comments with multiple arguments specified,
e.g.
/packit pull-from-upstream --with-pr-config --resolved-bugs rhbz#123. (packit-service#2346)
Week 6 in Packit
· One min read
Week 6 (February 6th – February 12th)
- Packit now searches for bugzilla about new release created by Upstream Release Monitoring to reference each time it syncs the release downstream. (packit#2229)
- We have introduced new CLI command
packit dist-git initthat initializes Packit configuration for release automation in dist-git repository. (packit#2225) - We have introduced new configuration options
require.label.presentandrequire.label.absent. By configuring these you can specify labels that need to be present or absent on a pull request for Packit to react on such PR. (packit-service#2333) - Interface for labels was unified and
labelsproperty for PullRequest and Issue now return list of PRLabel and IssueLabel respectively. (ogr#839)
Week 5 in Packit
· One min read
Week 5 (January 30th – February 5th)
packit validate-confignow checks whether the Upstream Release Monitoring for the package is correctly configured ifpull_from_upstreamjob is present in the configuration. (packit#2226)- There is a new global configuration option
parse_time_macrosthat allows to configure macros to be explicitly defined or undefined at spec file parse time. (packit#2222) - We have added additional retries and improvements for task processing. (packit-service#2326)