Skip to content

bitwarden-cli: 2024.12.0 -> 2025.1.3#381559

Closed
bobvanderlinden wants to merge 3 commits intoNixOS:masterfrom
bobvanderlinden:bitwarden-cli-2025.1.3
Closed

bitwarden-cli: 2024.12.0 -> 2025.1.3#381559
bobvanderlinden wants to merge 3 commits intoNixOS:masterfrom
bobvanderlinden:bitwarden-cli-2025.1.3

Conversation

@bobvanderlinden
Copy link
Member

https://github.com/bitwarden/clients/releases/tag/cli-v2025.1.3

The bitwarden-cli build was already broken due to dangling symlinks and the check that was recently introduced cross-repo. See #370750

2025.1.3 also introduced another breakage, where it now tries to download esbuild prebuilt binaries. Since there are 2 versions of esbuild it needs. I solved this problem the same way as was done in #381008

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Add a 👍 reaction to pull requests you find important.

esbuild binaries are being downloaded through npm. We can work around
this using an environment variable, but since there are 2 different
versions of esbuild being used in the lock file, we need to do some
juggling of this envvar.

Skipping those scripts also works and is less complex.
@ofborg ofborg bot added the 2.status: merge conflict This PR has merge conflicts with the target branch label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2.status: merge conflict This PR has merge conflicts with the target branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant