teleport_15: 15.4.21 -> 15.4.22, teleport_16: 16.4.6 -> 16.4.8, teleport_17: init at 17.0.1

[techknowlogick]

https://github.com/gravitational/teleport/releases/tag/v15.4.22
https://github.com/gravitational/teleport/releases/tag/v16.4.8
https://github.com/gravitational/teleport/releases/tag/v17.0.1

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:
  • 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/)
• 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.

[justinas]

Thanks for the PR.

Please make v17 the default as described. Afterwards, please also add an explicit test for v16 to nixos/tests/teleport.nix. v17 will be tested automatically, since the test has a case with the default pkgs.teleport.

[techknowlogick]

Thanks @justinas, I've adjusted this PR based on your feedback :)

[kaleocheng]

@techknowlogick seems this PR is kind of ready but just need minor change for the merge conflict. could you rebase it?

Edit: I’d also suggest splitting this PR into multiple smaller PRs—one for the 15/16 changes and another for the 17 initialization maybe. so we can easily backport the 15/16 changes to 24.11.

[JuliusFreudenberger]

@techknowlogick, do you want to continue working on this PR? Otherwise I am willing to take on the updates of teleport{15,16} and the init of teleport17 in separate PRs as suggested.

[justinas]

@techknowlogick, do you want to continue working on this PR? Otherwise I am willing to take on the updates of teleport{15,16} and the init of teleport17 in separate PRs as suggested.

I would recommend you to go ahead with making your PR as this PR has been hanging for a bit already, and Teleport moves quickly. 🙂

[techknowlogick]

Oh, yes please. Sorry for this one dropping off my radar. If you do create them, could you ping me as well since sometimes the automatic PR review requests sometimes don't work for this package

[JuliusFreudenberger]

I gave it a shot bumping teleport 15 and 16 in #376749, but faced problems with version 16. Maybe you can have a look there.

[techknowlogick]

Closing this due to conflicts, and alternative PRs.