Skip to content

CLOUDP-453196: Support vX.Y.Z release tags and drop the goreleaser tag_prefix - #143

Closed
fmenezes wants to merge 1 commit into
mongodb:mainfrom
fmenezes:CLOUDP-453196-release-process
Closed

fmenezes wants to merge 1 commit into
mongodb:mainfrom
fmenezes:CLOUDP-453196-release-process

Conversation

@fmenezes

Copy link
Copy Markdown
Contributor

Proposed changes

Jira ticket: https://jira.mongodb.org/browse/CLOUDP-453196

Twin of the Atlas CLI change (CLOUDP-453185 / mongodb/mongodb-atlas-cli#4837): make the release process use bare vX.Y.Z tags.

  1. build/package/.goreleaser.yml — drop the monorepo.tag_prefix: mongocli/ so goreleaser drives the release version from a bare vX.Y.Z tag (the first release after this merges must be tagged in the new format).
  2. scripts/release.sh — tag format switched from mongocli/vX.Y.Z to vX.Y.Z.
  3. RELEASING.md — manual-release instructions updated.

No git_tag_aliases change is needed (atlas had to add a v* alias): this project defines none, so git_tag_only variants trigger on any tag.

Testing

Further comments

Merge-order caveat: the first bare vX.Y.Z release should only be tagged after #142 (git-version.sh) and the windows_build_msi.sh follow-up noted there land, so the MSI artifact name is derived from the new-format tag. Part of the CLOUDP-397396 release-pipeline epic. The triage labeler check fails red on fork PRs (read-only GITHUB_TOKEN); all real CI checks pass.

…g_prefix

Drop the goreleaser monorepo tag_prefix so bare vX.Y.Z tags drive
releases (twin of CLOUDP-453185 / #4837), switch scripts/release.sh to
the vX.Y.Z tag format and update RELEASING.md. No git_tag_aliases change
needed: this project defines none, so git_tag_only variants trigger on
any tag.
@fmenezes fmenezes closed this Oct 28, 2026
@fmenezes
fmenezes deleted the CLOUDP-453196-release-process branch October 28, 2026 10:47
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