Repository navigation
Use the existing v1.0 tag for Phase 2 workflow callers - #3
Merged
Merged
Conversation
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.
Follow-up to #2, implementing the maintainer’s explicit instruction to move the already existing control tag rather than create v1. The API inventory contains only v1.0. Align the canonical caller, its exact-template contract test, and rollout documentation with @v1.0; all five caller PRs use the same reference. No Book-* or product-version tags are changed. Local verification: all 31 tests, catalog/profile drift, actionlint and whitespace checks pass. After green CI and merge, move only refs/tags/v1.0 in SNodeC/.github to this merged control commit, then continue the already-approved caller merges in dependency order.