Remove "v" prefix from release tags and titles#7
Conversation
Co-authored-by: nilsandrey <3579285+nilsandrey@users.noreply.github.com>
|
@copilot Update this PR description to have the expected sections for the Release pipeline used to update changelog and release I think. DescriptionType of Change
@copilot Update this PR description to have the expected sections for the Release pipeline used to update changelog and release I think. DescriptionType of Change
|
... Updated the PR description with the expected sections including |
There was a problem hiding this comment.
Pull request overview
This PR removes the v prefix from GitHub release tags and titles across the release pipeline, switching from the v#.#.# format to a bare #.#.# semver format. This aligns the release tag format with the manifest.json version field, which is relevant for the Obsidian community plugins marketplace (which auto-detects releases by matching the tag to manifest.json's version). The PR also updates the two existing CHANGELOG reference link URLs to use the new format.
Changes:
- Updated the release workflow to produce bare semver tags/titles and commit messages (no
vprefix). - Updated CHANGELOG.md reference links for the two existing releases (
1.0.0,1.0.1) to match the new format.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
.github/workflows/release.yml |
Removes v prefix from gh release create tag/title, changelog URL generation, and commit message |
CHANGELOG.md |
Updates existing release reference links from v1.0.x to 1.0.x tag format |
| Fix release workflow bump detection: correct broken regex (`\[xX\]` → `\[[xX]\]`), use temp file + `awk` markers for reliable multiline PR body handling, replace `echo | grep` with here-strings, and fall back to full-body scan when markers are missing. (PR #6) | ||
|
|
||
| [1.0.1]: https://github.com/nilsandrey/TextToolsPlugin/releases/tag/v1.0.1 | ||
| [1.0.1]: https://github.com/nilsandrey/TextToolsPlugin/releases/tag/1.0.1 |
There was a problem hiding this comment.
The CHANGELOG.md links for the already-published releases 1.0.0 and 1.0.1 now point to releases/tag/1.0.0 and releases/tag/1.0.1 respectively. However, the release tags for these versions were created by the old workflow using the v prefix (i.e., v1.0.0 and v1.0.1). Since no GitHub releases exist at the bare 1.0.0 / 1.0.1 tag URLs, these two links will be broken for all readers of the CHANGELOG.
To fix this, either:
- Manually create tag aliases
1.0.0and1.0.1in the GitHub repository that point to the same commits asv1.0.0andv1.0.1, or - Keep the existing release reference links pointing to the
v-prefixed tags (i.e., revert the CHANGELOG.md changes for these two entries), so that only new releases going forward use the bare semver tag format.
| - Full multi-selection support: all commands operate on every active editor selection independently. | ||
|
|
||
| [1.0.0]: https://github.com/nilsandrey/TextToolsPlugin/releases/tag/v1.0.0 | ||
| [1.0.0]: https://github.com/nilsandrey/TextToolsPlugin/releases/tag/1.0.0 |
There was a problem hiding this comment.
Same issue as the 1.0.1 link above: this link points to releases/tag/1.0.0, but the actual GitHub release for version 1.0.0 was published with the v-prefixed tag v1.0.0. The 1.0.0 tag does not exist, so this link will be broken. The existing release reference links for already-published versions should either continue to use the v-prefixed tag format they were published under, or new non-v tag aliases need to be created for those releases.
Description
Remove "v" prefix from release tags and titles, switching version tag format from
v#.#.#to#.#.#across the release pipeline and changelog.Type of Change
Changes Made
.github/workflows/release.yml: Stripvprefix fromgh release createtag/title, changelog URL generation, and commit message (4 locations)CHANGELOG.md: Update existing release reference links to match new#.#.#format (2 locations)✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.