feat: Introduce script to sync package versions with NPM registry #3929
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
Saadnajmi
force-pushed
the
sync-versions-output
branch
from
4739a69 to
af588ee
Compare
10 tasks
Collaborator
Author
|
JK beachball does this for us. |
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.
Platforms Impacted
Description of changes
We often have NPM publish issues where the pacakge version numbers are behind what was published to NPM. So.. I asked AI: "Could we write a script in the scripts/ folder that goes through every package.json, checks NPM for the latest package, and if they don't match, updates the local package.json version to match NPM?"
This is the output of GitHub Copilot with Claude Sonnet 4. I want to fix this up to not be the straight AI generated script, but I also want to unblock FURN. So publishing this PR with its output in a separate PR.
Verification
(how the change was tested, including both manual and automated tests)
Pull request checklist
This PR has considered (when applicable):