Repository navigation
Refresh published package validation and release guidance - #15
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
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.
The compatibility guide still told Windows users to wait for a release containing the working-directory fix, although v0.23.1 is published. Point affected v0.23.0 users to v0.23.1 and link the successful Linux/Windows published-package checks. Also mark the release commands as version-specific examples so maintainers do not reuse an existing tag.
Validation: published v0.23.1 package consumers passed on both platforms in run38532525783; local script suite passed16 tests, documentation links reviewed, and git diff --check passed. Documentation only; no release or asset changes.