woodpecker-*: 0.15.11 -> 1.0.0

[ambroisie]

Description of changes

Closes #246104. Release note here and blog post there.

Since #231513 has not been closed, I've decided to bump pnpm-lock-export to a fork which has v6 support, in order to package the front-end.

This release includes a lot of breaking changes.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• [] Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• 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/)
• 23.11 Release Notes (or backporting 23.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.

[ambroisie]

I have yet to test this on my infra, but uploading it now so that others can also try it out.

EDIT: seems to work.

[tek]

I tried using the new local backend with this, and it complains that it can't find plugin-git in the PATH, even if it's in systemPackages.

[ambroisie]

@tek you need to add it to the service's path (it can't access the system packages as a security measure).

See my dotfiles for an example.

[adamcstephens]

I tried using the new local backend with this, and it complains that it can't find plugin-git in the PATH, even if it's in systemPackages.

Should we configure the module to add this to the service path by default?

[ambroisie]

Should we configure the module to add this to the service path by default?

I think it's best not to bloat the closure of a service if it is not needed. As a middle-ground, I think we might be able to add a path option to the services.woodpecker-agents.agents.<name> attribute set (and make use of it in the example configuration).

EDIT: this can be done in a parallel PR, let's keep this one focused on updating the package.

[tek]

@tek you need to add it to the service's path (it can't access the system packages as a security measure).

See my dotfiles for an example.

oh thanks, I examined the systemd attributes for quite a while and couldn't figure out what the right way to do this was!

[adamcstephens]

I've upgraded my server and agent to this PR, and verified the CLI.

I'll add myself as maintainer after merge unless you want to add me in this PR.

[ambroisie]

I'll add myself as maintainer after merge unless you want to add me in this PR.

That's fine with me :-). I think you should be the author of the commit for adding yourself.

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/prs-already-reviewed/2617/1035

[pjjw]

hey thanks for doing this!