In 787af0f79f
I had to change ${go-modules} to $goModules to allow overrideAttrs to work;
However, env vars cannot contain -, so i had to change go-modules too.
This in turn broke nix-update because it uses the go-modules attr.
Instead of making nix-update more complicated, make go-modules naming match cargoDeps.
`fd --type f | xargs sd '\bgo-modules\b' 'goModules'`
and revert change to pkgs/applications/misc/dstask/default.nix
and pkgs/servers/http/dave/default.nix
and pkgs/os-specific/darwin/plistwatch/default.nix
release note added
This also required making a builder change.
See https://github.com/k3s-io/k3s/issues/7475 for context.
This applies to 1.26 and 1.27, it just happens that 1.27 also worked
without it
On unstable, we're now tracking
| version | EOL |
|---------|-----|
| 1.24 | 07/2023 |
| 1.25 | 10/2023 |
| 1.26 | 02/2024 |
| 1.27 | 06/2024 |
This commit adds 1.27 using the 1_26 builder introduced in the last
commit.
Notably, this commit also updates the 'update.sh' script to work for the
new setup I have here.
This is meant to make it easier to maintain multiple versions of the
package without having to copy+paste folders every time.
We can still copy+paste if the builders diverge enough to warrant it.
This version is no longer supported, as of roughly 1 week ago, according to [k8s upstream docs](https://kubernetes.io/releases/patch-releases/#non-active-branch-history).
There's additional discussion about the future of k3s versioning in #222604. This gets the simple uncontroversial change out of the way first to ensure people can't accidentally pick this unsupported version.
We dropped behind on releases for a bit due to our automatic update
script breaking.
This happened because of the traefik chart packaging changing
considerably. See the related upstream PR https://github.com/k3s-io/k3s/pull/6519
This updates our packaging to work with the new setup. Conveniently,
this also lets us drop a patch since chart packaging upstream has
simplified some too.
