Repository navigation
release: several release projects in one repository - #18
Merged
Merged
Conversation
added 2 commits
October 26, 2026 10:00
release.sh intent and release-intent.yml take a release-name: a release pull request of another project is a no-release for this one, whose version may not change (one release per pull request); mode refuses a merge title of another project. pr.sh release takes TAG_PREFIX (e.g. db-v) and WRITE_VERSION (the project's version recipe) from the environment, pr.sh merge a comma-separated list of version files. Tests in both suites, each guard mutation-checked.
A second release project tags git with its own prefix (db-v1.2.3) while its image keeps the tag the deployments read (v1.2.3). release-image takes image-tag-prefix (empty = tag-prefix) and uses the image tag for the registry check, the version label, {tag} and the published index; the git tag output stays as it was, an image-tag output joins it. Self-test: a dry run with db-v / v asserts both tags.
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.
For repositories with more than one release project (first: platform-db with
db-v*andmigrator-v*).release-intent.ymlinputrelease-name→release.sh intent: a release title naming another project is a no-release here; this project's version may not change in that PR.release.sh mode: withRELEASE_NAME, a merge title of another project is refused.pr.sh release:TAG_PREFIX,WRITE_VERSIONfrom the environment;pr.sh merge: comma-separated version files.release-image.yml:image-tag-prefix(empty =tag-prefix): git tagdb-v1.2.3, image tagv1.2.3; new outputimage-tag. Self-test job asserts both.Single-project repositories are unaffected (all defaults unchanged). Tests in both suites; each new guard mutation-checked.