ruby: 2.7.4 -> 2.7.5, 3.0.2 -> 3.0.3#147343
Conversation
|
This need to go to staging. |
|
The previous update also went straight to master: #129586 |
|
|
|
Is there anything we can do to pull this in? I'd love to get our rubies upgraded to 3.0.3. |
|
Backport failed for Please cherry-pick the changes locally. git fetch origin release-21.05
git worktree add -d .worktree/backport-147343-to-release-21.05 origin/release-21.05
cd .worktree/backport-147343-to-release-21.05
git checkout -b backport-147343-to-release-21.05
ancref=$(git merge-base 47b35f569e84eb6dbbcf0a9fc75d8729ab8837fd 26038de2256eae025045e4646d91a73285700ed3)
git cherry-pick -x $ancref..26038de2256eae025045e4646d91a73285700ed3 |
|
Successfully created backport PR #148254 for |
|
these updates going straight to master are really disruptive, because it causes rebuilds on master, and staging-next, and the release channel. Please use staging next time |
just because it was done before, doesn't mean it was right |
|
essentially, part of the reason why it takes so long for staging to get into master, is because of excessive rebuilds being piled on. |
Motivation for this change
Fixes 3 CVE's:
Things done
sandbox = trueset innix.conf? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)nixos/doc/manual/md-to-db.shto update generated release notes