Repository navigation
Prepare v1.0.1 release metadata and handoff - #13
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.
Promote the already deployed subscription improvements to v1.0.1 by aligning the root package/lock metadata and recording release authorization and scope. This supersedes the previous wait-for-user-acceptance gate; it does not assert new inbox acceptance.
Runtime code, dependency resolution, schema, production configuration and quotas are unchanged. Preserve the v1.0.0 tag. The annotated v1.0.1 tag and Sites deployment will be recorded only after their actual completion.
Validation: package and lock versions agree; diff checks pass. Required verify executes the existing 119 tests, type/content/audit/lint/build/HTTP/link gates and original bundle budgets.