Repository navigation
Validate published changelog metadata before release builds - #165
Merged
Merged
Conversation
Steadyx
marked this pull request as ready for review
October 18, 2026 15:06
9 tasks done
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.
What changed
Require one published changelog entry matching the configured release version before release builds and in
qualityGate. Ordinary debug builds andqualityCheckremain independent of release readiness. Add six regression tests and release guidance.Updated with current
main: the app remains at 1.4.0 / code 16. No release, tag, or signed artifact is created.Risk
Release validation reuses debug unit-test compilation. Runtime app behavior is unchanged.
Validation
./gradlew qualityCheck— 925 JVM tests passed./gradlew qualityGate, including:app:validateChangelog, passed locally on currentmaingit diff --checkQuality policy
ignoreFailures, broad exclusion, or threshold relaxation added