Repository navigation
Prepare repo for the 5.7 dev cycle - #36
Merged
Merged
Conversation
TurboGit
reviewed
Jun 20, 2026
Member
There was a problem hiding this comment.
When/where this release notes should be used?
Collaborator
Author
There was a problem hiding this comment.
That would be for release 5.8.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Now that
release-5.6.0is cut andmodels-5.6.xis branched, master moves on to 5.7 dev work. Two small bookkeeping changes to make that smoother:RELEASE_NOTES.md: reset to a 5.8.0 placeholder so the file isn't carrying the 5.6.0 announcement through dev.releases-index.json: map5.7.0tonightly-5.7.0so darktable nightlies can resolve their model set during the cycle.Also unrelated but bundled-in CI cleanup:
.github/workflows/check-pr.yml: addpaths-ignoreso docs-only,tools/-only,releases-index.json-only, andnightly.yml/release.yml-only PRs no longer trigger the full model validation matrix. Saves several minutes per cosmetic change.