feat(schema): add seeded_from for cross-repo split version continuity - #660
Open
hdamker wants to merge 1 commit into
Open
feat(schema): add seeded_from for cross-repo split version continuity#660hdamker wants to merge 1 commit into
hdamker wants to merge 1 commit into
Conversation
Repository splits move APIs into a new repository whose own release history is empty, so RA's version calculation would otherwise restart pre-release numbering at rc.1/alpha.1 and collide with versions already published for the API in the predecessor repository. seeded_from declares the last published rc/alpha version as a one-time, hand-typed fact rather than a live cross-repo lookup.
hdamker
requested review from
rartych,
soadeyemo and
tanjadegroot
as code owners
September 2, 2026 11:49
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
1 participant
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 type of PR is this?
enhancement/feature
What this PR does / why we need it:
This is only relevant for repositories created by splitting APIs out of an existing repository. Adds an optional
seeded_fromsection torelease-plan.yaml's schema, letting a repository declare that one or more of its APIs continue a pre-release (rc/alpha) version chain seeded from a predecessor repository. This is needed when APIs move into a new repository through a repository split, so Release Automation doesn't restart pre-release numbering atrc.1/alpha.1and collide with a version already published for that API in the predecessor. The seed is a one-time, hand-declared fact (provenance fields plus per-APIlast_rc_api_version/last_alpha_api_version), not a live cross-repo lookup.Which issue(s) this PR fixes:
Part of camaraproject/tooling#441
Special notes for reviewers:
Schema-only change. The vendored schema copy in
hdamker/toolingand the version-calculation logic that readslast_rc_api_version/last_alpha_api_versionare a separate, following PR, per the sequencing in tooling#441.Changelog input
Additional documentation