Skip to content

chore(release): publish a dev build's prerelease tag as a GitHub prerelease - #68

Merged
antoinetoussaint-byte merged 1 commit into
mainfrom
chore/dev-builds-are-prereleases
Sep 24, 2026
Merged

antoinetoussaint-byte merged 1 commit into
mainfrom
chore/dev-builds-are-prereleases

Conversation

@antoinetoussaint-byte

Copy link
Copy Markdown
Contributor

Summary

codefly publish dev refuses to run here:

.goreleaser.yaml would publish a dev tag as a full release (and mark it Latest); set `release: {prerelease: auto}` in it before publishing dev builds

This adds release: prerelease: auto, the same setting and comment service-go-grpc carries (#137). A v<version>-dev.<sha> tag becomes a GitHub prerelease, never Latest, so version: latest can never resolve to a dev build. Release tags are unaffected.

Classification: a fix to this repository's release configuration, which is what the CLI guard names.

Test plan

  • Diff is config-only.
  • Not verified: that a release tag still publishes as Latest. That rests on goreleaser's documented auto behaviour, as in service-go-grpc.

🤖 Generated with Claude Code

…elease

`codefly publish dev` refuses to run while .goreleaser.yaml would publish
its v<version>-dev.<sha> tag as a full release marked Latest. This is the
same setting service-go-grpc carries (#137).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@antoinetoussaint-byte
antoinetoussaint-byte merged commit 72f3113 into main Sep 24, 2026
3 checks passed
@antoinetoussaint-byte
antoinetoussaint-byte deleted the chore/dev-builds-are-prereleases branch September 24, 2026 23:23
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