philipp/uncloud
1
0
Fork 0
mirror of https://github.com/psviderski/uncloud.git synced 2026-11-10 04:34:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore(mise): add mise release task to release with GoReleaser

Browse Source
This commit is contained in:
Pasha Sviderski
2026-11-06 20:41:27 +10:00
parent 6a64bddf27
commit 24b4837d08
2 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mise.toml
+6
View File
@@ -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 --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] [tasks.uc]
description = "Run the Uncloud CLI" description = "Run the Uncloud CLI"
raw_args = true raw_args = true
website/docs/10-release-notes/v0.22.0.md
+3 -3
View File
@@ -12,9 +12,9 @@ This release makes **cluster storage for Caddy the default**, adds **service and
## ⚠️ Heads-up before upgrading {#heads-up-before-upgrading} ## ⚠️ 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` 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. - `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. - 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 ## Cluster storage for Caddy by default