teleport: add note to changelog about upgrade process
This commit is contained in:
parent
3a60214cb3
commit
8de9bf9112
1 changed files with 3 additions and 0 deletions
|
@ -414,3 +414,6 @@ The module update takes care of the new config syntax and the data itself (user
|
||||||
`virtualisation.fileSystems = lib.mkForce { };`.
|
`virtualisation.fileSystems = lib.mkForce { };`.
|
||||||
|
|
||||||
- The `electron` packages now places its application files in `$out/libexec/electron` instead of `$out/lib/electron`. Packages using electron-builder will fail to build and need to be adjusted by changing `lib` to `libexec`.
|
- The `electron` packages now places its application files in `$out/libexec/electron` instead of `$out/lib/electron`. Packages using electron-builder will fail to build and need to be adjusted by changing `lib` to `libexec`.
|
||||||
|
|
||||||
|
- `teleport` has been upgraded from major version 12 to major version 14. Please see upstream [upgrade instructions](https://goteleport.com/docs/management/operations/upgrading/) and release notes for versions [13](https://goteleport.com/docs/changelog/#1300-050823) and [14](https://goteleport.com/docs/changelog/#1400-092023). Note that Teleport does not officially support upgrades across more than one major version at a time. If you're running Teleport server components, it is recommended to first upgrade to an intermediate 13.x version by setting `services.teleport.package = pkgs.teleport_13`. Afterwards, this option can be removed to upgrade to the default version (14).
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue