Update npm deprecation notices to reflect current status #2931
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.
Summary
npm classic tokens were permanently revoked on December 9, 2025. Updated the documentation to use time-robust language instead of referencing the mid-November 2025 date that has now passed.
Changes made:
publishing-to-npm.mdxto use present tense ("npm has deprecated") instead of future tense with specific datesAlso verified:
fernExtensions.tsReview & Testing Checklist for Human
Notes
The package-lock.json file that was accidentally added in the first commit has been removed.
Link to Devin run: https://app.devin.ai/sessions/2a965b5200d14bd0a7369d735bd83f3b
Requested by: Fern Support (info@buildwithfern.com)