This updates to the latest version of nixpkgs-unstable. This is in response to the need to update localstack from 1.4.0 to >2.3.2.
Details
- Reviewers
ashoat varun bartek atul - Group Reviewers
Restricted Owners Package (Owns No Changed Paths) - Commits
- rCOMMda579abcb51f: [nix] Upgrade to latest version of nixpkgs-unstable
Successfully ran nix develop with working build environment
Diff Detail
- Repository
- rCOMM Comm
- Branch
- update_nixpkgs_unstable
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
This would bring forward a bunch of dependencies, right?
Should we take some sort of inventory of what's being updated to at least see if any might be of concern?
For example, when I run which pod before this diff:
/nix/store/n3nhjnv92sx1pxhsiiz44796r2hhxx06-cocoapods-1.12.1/bin/pod
and after
/nix/store/qrdahdk9s7wdc7wd5r63gzk6kfhp4vnn-cocoapods-1.14.3/bin/pod
we're bumping the version cocoapods, so we will necessarily have changes to Podfile.lock.
At a minimum, we should run yarn cleaninstall and stage the changes to Podfile.lock in this diff or a follow-up diff that lands immediately.
Ideally, I think we should just make a list of everything that would get updated and flag the 3-4 dependencies that might be relevant and do some minimal investigation or thinking about whether problems might arise.
Another thing that immediately comes to mind is
nodejs-18.17.1/bin/node to nodejs-20.10.0/bin/node
Good call @atul. If we’re updating Node we should probably also update the versions in keyserver/Dockerfile and keyserver/.nvmrc to match
services/electron-update-server/Dockerfile | ||
---|---|---|
1 ↗ | (On Diff #35569) | Yes would be good to upgrade I think… Node 16 is old |