Repository navigation
Prepare registry release v1.0.1 - #7
Merged
Merged
Conversation
thomashoneyman
changed the title
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.
Configures registry publication as 1.0.1 to match the planned v1.0.1 Git tag, with MIT licensing and the existing repository location. Dependency bounds are unchanged.
Preserves the historical v1.0.0 changelog entry and records only the migration/tooling work under v1.0.1. Verify the planned release date before tagging.
Strict/pedantic build, formatting, lint, and full registry dependency-closure checks pass. No existing tests; one dev-only Spago advisory remains.