Prepare Webdoc 2.2.1 patch release - #204
Open
ShukantPal wants to merge 2 commits into
Open
ShukantPal wants to merge 2 commits into
ShukantPal wants to merge 2 commits into
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.
Stack position
This is stack item 3 of 3. It is based on
masterand should merge after: (1) CI baseline and (2) dependency modernization. It intentionally does not modify CI workflows or third-party dependency versions; the only dependency-range edits are Rush-generated@webdoc/*lockstep release updates.Release preparation
@webdoc/*packages from 2.2.0 to the lockstep patch release 2.2.1.@webdoc/parser,@webdoc/example, and@webdoc/tests. No package was published, deprecated, or removed.Owner publish command (after merge)
From a supported Node.js version with npm credentials configured, run:
This publishes the already-prepared 2.2.1 versions; do not run
rush versionagain first.Legacy npm custody recommendation — owner decision required
@webdoc/parser(1.6.6, ~2,893 monthly downloads): recommendnpm deprecatewith a migration message to@webdoc/language-parser; the successor is maintained in Rush and the deprecation preserves installs while giving consumers a clear route.@webdoc/example(1.0.0, ~220/month): recommendnpm deprecate; it is an unpublished reference-only example, and consumers should use@webdoc/cliplus copied configuration patterns.@webdoc/tests(1.0.0, ~108/month): recommendnpm deprecate; it is an unmaintained integration fixture outside the Rush project list, and consumers should use root Rush test commands or@webdoc/clipublic APIs.These are recommendations only. This PR deliberately does not invoke
npm deprecate.