Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update dependencies to latest versions across multiple packages #2266

Merged
merged 4 commits into from
Mar 7, 2025

Conversation

mattheworris
Copy link
Collaborator

@mattheworris mattheworris commented Mar 6, 2025

Goal

The goal of this PR is to update the npm packages in the various js directories.

Closes #2262

Discussion

  • Used ncu to update all the packages to the latest version.
  • No Major versions were updated except api-augment/globals 15.14.0 => 16.0.0

Checklist

  • Updated Pallet Readme?
  • Updated js/api-augment for Custom RPC APIs?
  • Design doc(s) updated?
  • Unit Tests added?
  • e2e Tests added?
  • Benchmarks added?
  • Spec version incremented?

@mattheworris mattheworris requested a review from wilwade as a code owner March 6, 2025 22:56
@mattheworris mattheworris linked an issue Mar 6, 2025 that may be closed by this pull request
3 tasks
@mattheworris mattheworris self-assigned this Mar 6, 2025
@mattheworris mattheworris requested review from a team, shannonwells, enddynayn, aramikm, claireclark1 and JoeCap08055 and removed request for a team March 6, 2025 23:02
Copy link
Collaborator

@wilwade wilwade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

  • Reviewed code
  • Checked out and reviewed package updates

Copy link

codecov bot commented Mar 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions github-actions bot added the metadata-changed Metadata has changed since the latest full release label Mar 7, 2025
@@ -401,7 +401,7 @@ pub const VERSION: RuntimeVersion = RuntimeVersion {
spec_name: create_runtime_str!("frequency"),
impl_name: create_runtime_str!("frequency"),
authoring_version: 1,
spec_version: 141,
spec_version: 143,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need to update the chain spec version if all we updated was the JS packages, do we?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No we don't, I was checking the rust pipeline in CI to compare against local issues.
I will remove the spec bump.

…ation (force ci to run rust tests)"

This reverts commit 3621b30.
@github-actions github-actions bot removed the metadata-changed Metadata has changed since the latest full release label Mar 7, 2025
Copy link
Collaborator

@enddynayn enddynayn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@mattheworris mattheworris merged commit 6be0bbe into main Mar 7, 2025
28 checks passed
@mattheworris mattheworris deleted the 2262-upgrade-npm-packages branch March 7, 2025 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade NPM packages
4 participants