Skip to main content

· One min read
Matej Focko

Week 33 (August 11th – August 17th)​

  • The ForgejoService.get_project_from_url() method has been updated to ensure repository names are parsed accurately. It now correctly removes the .git extension from the repository name, addressing an issue where the extension was previously retained. (ogr#1005)

· One min read
Alžběta Kučerová

Week 31 (July 28th – August 3rd)​

  • There is a new configuration option skip_missing_branched_composes that, when enabled, skips test jobs for freshly branched Fedora versions that don't have a corresponding Testing Farm compose yet. (packit-service#3160)
  • A fix has been implemented for a bug causing Packit to crash when adding a comment reaction on GitLab. (ogr#995)

· One min read
Nikola Forró

Weeks 29 and 30 (July 13th – July 27th)​

  • The ogr library now correctly handles the Forgejo error commit flag, resolving an issue that previously caused it to fail during internal mapping. (ogr#991)
  • Log Detective run overview on the dashboard now, for successful runs, shows also a list of snippets, grouped by file, in expandable sections. (dashboard#540) Log Detective snippets

· One min read
Nikola Forró

Week 27 (July 1st – July 7th)​

  • When a package is configured to consume mutiple release streams and release-monitoring.org detects multiple releases at the same time, if a pull-from-upstream job run for one released version fails, only that one is retried and the rest are unaffected and properly processed. Before this fix it could happen that a failed job run for one released version could prevent other released versions from being processed at all. (packit-service#3147)