Skip to content
This repository was archived by the owner on Apr 26, 2026. It is now read-only.

Bump VERSION to 3.7.0 (final Canasta-Go release; mirrors to new Canasta-CLI) - #743

Merged
cicalese merged 3 commits into
mainfrom
bump-version-3.7.0
Apr 26, 2026
Merged

Bump VERSION to 3.7.0 (final Canasta-Go release; mirrors to new Canasta-CLI)#743
cicalese merged 3 commits into
mainfrom
bump-version-3.7.0

Conversation

@cicalese

Copy link
Copy Markdown
Contributor

Summary

One-line bump: VERSION 3.6.33.7.0. This is the trigger that fires the release workflow.

Phase 6.b in Canasta-Ansible #357 (master tracking for the v4.0.0 release).

DO NOT merge before #741

#741 adds the deprecation warning + cross-repo mirror plumbing. If this PR lands before #741, the workflow that fires will be the old workflow:

  • ✅ Regular publish step → creates Canasta-Go/releases/v3.7.0 with the four binaries (built without the deprecation warning, since cmd/root/root.go doesn't have it yet on main).
  • ❌ No mirror step → the new Canasta-CLI repo (formerly Canasta-Ansible) gets no v3.7.0 release → legacy canasta upgrade clients hit a 404 from api.github.com/repos/CanastaWiki/Canasta-CLI/releases/latest.

Correct order: merge #741 first, then merge this. Either:

What happens when this merges (after #741 is in)

The workflow fires:

  1. Build matrix produces canasta-linux-amd64, canasta-linux-arm64, canasta-darwin-amd64, canasta-darwin-arm64 — the real Canasta CLI Go binaries with the deprecation warning baked into PersistentPreRun.
  2. Regular publish creates Canasta-Go/releases/v3.7.0 with the four binaries attached.
  3. Mirror step mints a token from the CanastaWiki GitHub App (#742) and creates the same release in CanastaWiki/Canasta-CLI with the same four binaries.

After the workflow succeeds:

$ curl -fsSL https://api.github.com/repos/CanastaWiki/Canasta-CLI/releases/latest | jq .tag_name
"v3.7.0"

Legacy canasta upgrade from a 3.6.x VM should self-update to 3.7.0 successfully; subsequent commands print the deprecation warning to stderr but work normally.

Test plan

  • Confirm vars.RELEASE_BOT_APP_ID and secrets.RELEASE_BOT_PRIVATE_KEY are set at the org level (per Set up CanastaWiki GitHub App for cross-repo release mirror (post-rename) #742) before merging — otherwise the mirror step skips and we end up in the same broken state as merging without Add deprecation warning and cross-repo release mirror (replaces #740) #741.
  • After merge, watch the Go build workflow run on main and confirm the release job's "Mirror release to CanastaWiki/Canasta-CLI" step succeeds (not skipped).
  • Verify both releases:
    • gh release view v3.7.0 --repo CanastaWiki/Canasta-Go --json assets --jq '.assets[].name'
    • gh release view v3.7.0 --repo CanastaWiki/Canasta-CLI --json assets --jq '.assets[].name'
  • On a clean VM with Canasta CLI 3.6.x: run canasta upgrade. Confirm it self-updates to 3.7.0 and subsequent commands show the deprecation warning.

Triggers the release workflow on merge:
  - Builds the four Go binaries (canasta-{linux,darwin}-{amd64,arm64})
    with the deprecation warning baked in (added in #741).
  - Regular publish step creates Canasta-Go/releases/v3.7.0.
  - Cross-repo mirror step (added in #741) creates the same release
    in CanastaWiki/Canasta-CLI using the GitHub App token, so legacy
    3.x clients hitting api.github.com/repos/CanastaWiki/Canasta-CLI/
    releases/latest find a working v3.7.0 binary.

Phase 6.b in CanastaWiki/Canasta-CLI#357 (master tracking issue
for the v4.0.0 release / rename arc).

DO NOT merge before #741 is merged. If this lands first, the workflow
will publish v3.7.0 to Canasta-Go but skip the mirror step (it doesn't
exist yet on main), leaving the new Canasta-CLI repo with no releases
and breaking legacy canasta upgrade.
End-of-life release of the Canasta-Go CLI: adds the deprecation warning
from #741, mirrors release artifacts to CanastaWiki/Canasta-CLI, no
other functional changes. release_date placeholder gets filled in
post-merge once the workflow tags the release.
@cicalese
cicalese merged commit 3363a70 into main Apr 26, 2026
2 checks passed
@cicalese
cicalese deleted the bump-version-3.7.0 branch April 26, 2026 02:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants