Repository navigation
yarn-berry: 4.14.1 -> 4.18.0 - #524710
yarn-berry: 4.14.1 -> 4.18.0#524710r-ryantm wants to merge 1 commit into
Conversation
nixpkgs-ci
Bot
added
8.has: package (update)
There was a problem hiding this comment.
They bumped __metadata.version again... https://github.com/yarnpkg/berry/pull/7135/changes#diff-51e4f558fae534656963876761c95b83b6ef5da5103c4adef6768219ed76c2deR5
We will need to update the patches as we update yarn again. See #513745
❌
|
c56b188 to
04788e1
Compare
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript. meta.description for yarn-berry is: Fast, reliable, and secure dependency management meta.homepage for yarn-berry is: https://yarnpkg.com/ meta.changelog for yarn-berry is: https://github.com/yarnpkg/berry/releases/tag/@yarnpkg/cli/4.16.0 Updates performed
To inspect upstream changesImpactChecks done
Caution A test defined in
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript. meta.description for yarn-berry is: Fast, reliable, and secure dependency management meta.homepage for yarn-berry is: https://yarnpkg.com/ meta.changelog for yarn-berry is: https://github.com/yarnpkg/berry/releases/tag/@yarnpkg/cli/4.17.0 Updates performed
To inspect upstream changesImpactChecks done
Caution A test defined in
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
04788e1 to
d602ec4
Compare
Would you mind opening a PR for that? |
I don't mind opening a PR. But I do mind spending 4 days again ensuring nothing broke (this time also hopefully ensuring update scripts don't break) only for upstream to bump the metadata version again. Let me figure out a more resilient way to be able to update Yarn with minimal effort in case they pull this stunt again. |
d602ec4 to
25de88b
Compare
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript. meta.description for yarn-berry is: Fast, reliable, and secure dependency management meta.homepage for yarn-berry is: https://yarnpkg.com/ meta.changelog for yarn-berry is: https://github.com/yarnpkg/berry/releases/tag/@yarnpkg/cli/4.17.1 Updates performed
To inspect upstream changesImpactChecks done
Caution A test defined in
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
25de88b to
19a112f
Compare
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript. meta.description for yarn-berry is: Fast, reliable, and secure dependency management meta.homepage for yarn-berry is: https://yarnpkg.com/ meta.changelog for yarn-berry is: https://github.com/yarnpkg/berry/releases/tag/@yarnpkg/cli/4.18.0 Updates performed
To inspect upstream changesImpactChecks done
Caution A test defined in
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages. Maintainer pingscc @ryota-ka @pyrox0 @DimitarNestorov for testing. Tip As a maintainer, if your package is located under |
|
@DimitarNestorov is it still true that we need to update the patches? I tried building mastodon on this branched rebased against master and invalidated the vendor hash, too, and it seemed to work for me. |
nixpkgs-ci
Bot
removed
the
2.status: merge-bot eligible
Current version of Mastodon in master (v4.6.6) has an already updated to lock file metadata version 10 (Yarn v4.15) so no patch needed there: https://github.com/mastodon/mastodon/blame/v4.6.6/yarn.lock#L5 |
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for yarn-berry is: Fast, reliable, and secure dependency management
meta.homepage for yarn-berry is: https://yarnpkg.com/
meta.changelog for yarn-berry is: https://github.com/yarnpkg/berry/releases/tag/@yarnpkg/cli/4.15.0
Updates performed
To inspect upstream changes
Impact
Checks done
Caution
A test defined in
passthru.testsdid not pass.Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from the cache:
(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the
trusted-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-reviewresultGenerated using
nixpkgs-review.Command:
nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'Commit:
c56b1888ea68f95368cfb7023a6093d1167ee90cx86_64-linux❌ 186 packages failed to build:
✅ 1 package built:
Maintainer pings
cc @ryota-ka @pyrox0 @DimitarNestorov for testing.
Tip
As a maintainer, if your package is located under
pkgs/by-name/*, you can comment@NixOS/nixpkgs-merge-bot mergeto automatically merge this update using thenixpkgs-merge-bot.