Repository navigation
docs: use stable release identity in caller qualification - #663
Merged
Merged
Conversation
Signed-off-by: transitrix <automation@transitrix.com>
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.
GitHub draft HTML slugs can change when notes are edited. Replace the transient untagged locator in the qualified caller receipt with the stable release collection, numeric release ID, declared tag and API identity. Source commit and CLI/VSIX hashes stay unchanged; no package or runtime behavior changes.
Validation: documentation lint and whitespace checks passed. Exact archive/UI qualification remains bound to Studio e1a4994679a6012cbf88931076b07d8c03da2b00; no model or artifact re-execution is implied. This follow-up changes one receipt file only and does not publish a release.