Skip to content

release v1.1.3 — automate Homebrew + fix version constant - #3

Merged
jams24 merged 1 commit into
mainfrom
release-v1.1.3
Jul 1, 2026
Merged

release v1.1.3 — automate Homebrew + fix version constant#3
jams24 merged 1 commit into
mainfrom
release-v1.1.3

Conversation

@jams24

@jams24 jams24 commented Jul 1, 2026

Copy link
Copy Markdown
Owner

Supersedes #2 (includes the same version bump + npm README fix, plus CI improvements).

Changes

  • Version constant fix: proto.Version is now a var injected at build time via goreleaser ldflags (-X .../proto.Version={{ .Version }}). The CLI/server now report the real release tag instead of a hardcoded 1.0.15. (Verified: ldflag injection works.)
  • Automated Homebrew: goreleaser brews: block auto-updates the jams24/homebrew-deployzy formula (version + sha256) on every release — no more manual formula edits.
  • Bump all packages → 1.1.3
  • Rebrand npm-package/README.md (was still ServerMe)

⚠️ One-time setup before tagging v1.1.3

The Homebrew automation needs a token (it's the only cross-repo push, so it can't be OIDC):

  1. Create a fine-grained PAT: github.com/settings/tokens?type=beta → repo access = only jams24/homebrew-deployzy → permission Contents: Read and write → Generate.
  2. Add it as a repo secret: jams24/deployzy → Settings → Secrets and variables → Actions → New secret → name HOMEBREW_TAP_TOKEN, paste the PAT.

Release

After merging + adding the secret: git tag v1.1.3 && git push origin main --tags → CI publishes 1.1.3 to npm×2 + PyPI, cuts the GitHub release, and auto-updates the Homebrew formula.

- proto.Version const→var, injected at build time via goreleaser ldflags (binary now reports the release tag, not a hardcoded 1.0.15)
- goreleaser brews: block auto-updates jams24/homebrew-deployzy formula each release (needs HOMEBREW_TAP_TOKEN secret)
- bump all packages to 1.1.3
- rebrand npm-package/README.md (was still ServerMe)
@jams24
jams24 merged commit a322e0c into main Jul 1, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant