diff --git a/mise.toml b/mise.toml index 67802b19..52eda0d8 100644 --- a/mise.toml +++ b/mise.toml @@ -76,6 +76,12 @@ protoc --go_out=. --go_opt=paths=source_relative --go-grpc_out=. --go-grpc_opt=p --proto_path=. --proto_path=api/pb/vendor api/pb/*.proto pkg/distlock/grpc/*.proto """ +[tasks.release] +description = "Create a draft GitHub release with GoReleaser" +# The 1Password CLI resolves op:// secret references in the environment, e.g. GITHUB_TOKEN loaded from .env. +# Extra arguments are passed to goreleaser, e.g. 'mise run release --release-notes data/release-notes-X.Y.Z.md'. +run = "op run -- goreleaser release --clean --draft" + [tasks.uc] description = "Run the Uncloud CLI" raw_args = true diff --git a/website/docs/10-release-notes/v0.22.0.md b/website/docs/10-release-notes/v0.22.0.md index 95a0da0a..1f0edd41 100644 --- a/website/docs/10-release-notes/v0.22.0.md +++ b/website/docs/10-release-notes/v0.22.0.md @@ -12,9 +12,9 @@ This release makes **cluster storage for Caddy the default**, adds **service and ## ⚠️ Heads-up before upgrading {#heads-up-before-upgrading} -- **`uc caddy deploy` now deploys the Uncloud Caddy image with cluster storage** ([22b1c68](https://github.com/psviderski/uncloud/commit/22b1c68)). Upgrading Uncloud doesn't touch your running Caddy. But the next `uc caddy deploy` switches it to the new image and storage. Caddy doesn't copy certificates between storage backends, so it will reissue them unless you migrate them first. Read [Upgrading from earlier versions](/docs/concepts/ingress/cluster-storage-for-caddy#upgrading-from-earlier-versions) before you redeploy Caddy. -- **`uc caddy deploy` requires the 0.22.0 daemon on all machines.** Upgrade the daemons first. -- **Machine names must be valid DNS labels** ([ce1c6bd](https://github.com/psviderski/uncloud/commit/ce1c6bd)). This means lowercase letters, numbers, and hyphens, up to 63 characters. The names `rr` and `nearest` are reserved, and a name can't look like a machine ID. This applies when you add or rename a machine. +- `uc caddy deploy` now deploys the Uncloud Caddy image with cluster storage ([22b1c68](https://github.com/psviderski/uncloud/commit/22b1c68)). Upgrading Uncloud doesn't touch your running Caddy. But the next `uc caddy deploy` switches it to the new image and storage. Caddy doesn't copy certificates between storage backends, so it will reissue them unless you migrate them first. Read [Upgrading from earlier versions](/docs/concepts/ingress/cluster-storage-for-caddy#upgrading-from-earlier-versions) before you redeploy Caddy. +- `uc caddy deploy` requires the 0.22.0 daemon on all machines. Upgrade the daemons first. +- Machine names must be valid DNS labels ([ce1c6bd](https://github.com/psviderski/uncloud/commit/ce1c6bd)). This means lowercase letters, numbers, and hyphens, up to 63 characters. The names `rr` and `nearest` are reserved, and a name can't look like a machine ID. This applies when you add or rename a machine. ## Cluster storage for Caddy by default