-
Notifications
You must be signed in to change notification settings - Fork 36
Update the nightly tests to run the latest published version of npm packages #87
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
base: master
Are you sure you want to change the base?
Conversation
… Noir version mapping
…package versions based on Noir version mapping
|
Hi @critesjosh . |
|
Hi @critesjosh and @signorecello 👋, Just a gentle reminder to please take a moment to review this PR when you get a chance. Thanks a lot for your time and support! |
|
Hi @critesjosh. |
|
Hi @critesjosh and @signorecello 👋, Just a gentle reminder to please take a moment to review this PR when you get a chance. Thanks a lot for your time and support! |
|
Hi @critesjosh and @signorecello 👋, Just a gentle reminder to please take a moment to review this PR when you get a chance. Thanks a lot for your time and support! |
1 similar comment
|
Hi @critesjosh and @signorecello 👋, Just a gentle reminder to please take a moment to review this PR when you get a chance. Thanks a lot for your time and support! |
Hi @critesjosh
Description
This PR updates the nightly continuous integration (CI) workflows to automatically upgrade npm package dependencies to their latest published versions before running tests. This helps detect breaking changes from upstream packages early and ensures our test suite is always validating against the newest dependency versions.
Problem*
Resolves noir-lang/noir-examples/issues/86
Summary*
Nightly CI workflows now upgrade npm package dependencies to the latest published versions before running tests, ensuring compatibility with upstream changes and improving reliability. This is done using
npm-check-updates(ncu -u) in the nightly scheduled jobs for all relevant frontend projects.Additional Context
This change helps detect breaking changes in dependencies early by running the latest package versions in our test suites. It affects the nightly CI workflows for projects such as
recursion/js,solidity-example/js, andweb-starter/web/*.PR Checklist*
cargo fmton default settings.