Repository navigation
[BUG](ci) Fix release title format - #716
Merged
Merged
Conversation
…by vanity tag Fixes #715 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: John McCall <john@overturemaps.org>
🗺️ Schema reference docs preview is live!
Note ♻️ This preview updates automatically with each push to this PR. |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The changes are small, consistent with the PR description, and limited to release metadata/title formatting plus corresponding documentation updates.
Pull request overview
This PR fixes GitHub Release title formatting produced by the create-package-release composite action, aligning titles with how GitHub actually displays them (no markdown rendering) and keeping the umbrella overture-schema releases visually continuous via the legacy bare v<version> series.
Changes:
- Update release title generation to use
<package> v<version>, and use the vanity tag (e.g.,v2.0.0) as the title when a legacy bare tag is also created. - Enhance the dry-run step summary to print the computed release title.
- Update versioning documentation to reflect the corrected release-title scheme and the continued bare-tag series (
… v1.18.0).
File summaries
| File | Description |
|---|---|
| docs/versioning.md | Updates documented tag/title scheme and clarifies umbrella release titling for legacy bare tags. |
| .github/actions/create-package-release/action.yml | Computes correct gh release create --title value and surfaces it in dry-run output. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Francisco Jiménez (jjcfrancisco)
approved these changes
Sep 2, 2026
Francisco Jiménez (jjcfrancisco)
left a comment
Francisco Jiménez (jjcfrancisco)
left a comment
Member
There was a problem hiding this comment.
Nice
Seth Fitzsimmons (sethfitz)
approved these changes
Sep 4, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
create-package-releasetitled every 2.0.0 release`<package>` 2.0.0, backticks included, since release titles aren't rendered as markdown. Titles are now<package> v<version>, and a release with a vanity tag takes that tag as its title so the umbrella series staysv1.18.0->v2.0.0.The 13 live 2.0.0 releases were already retitled by hand with
gh release edit; this makes the action match. The title is pure gh meta, not the actual tag name.Fixes #715
Reference
Testing
Shell-only change to a composite action; no unit coverage exists for it. The dry-run step summary now prints the computed title so the next release run shows it before anything is created.
Checklist