Clarified the status of version 3.2 and added information about 3.3 in contributing#5028
Merged
Clarified the status of version 3.2 and added information about 3.3 in contributing#5028
Conversation
handrews
approved these changes
Oct 9, 2025
karenetheridge
approved these changes
Oct 9, 2025
Member
Author
|
Thanks for the quick reviews. I'm not sur why the CI failed here (probably because it came from a fork?). @ralfhandl a little help please? |
ralfhandl
approved these changes
Oct 9, 2025
Contributor
npmjs.org occasionally responds with 403 instead of 200 when checking links to it. Maybe the link checker is misidentified as an "attacker". 🤷♂️ |
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
4 participants
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.
Since we've released 3.2.0, this clarifies which branch is the upcoming version in the contributing guidelines