🌐 US-Proxy
class="logged-out env-production page-responsive" style="word-wrap: break-word;" >
Skip to content

fix(scripts/releaser): remove doubled "v" in release calendar latest release link - #27261

Merged
mtojek merged 1 commit into
release/2.34from
fix/release-calendar-doubled-version-prefix-2.34
Jul 15, 2026
Merged

fix(scripts/releaser): remove doubled "v" in release calendar latest release link#27261
mtojek merged 1 commit into
release/2.34from
fix/release-calendar-doubled-version-prefix-2.34

Conversation

@mtojek

@mtojek mtojek commented Jul 15, 2026

Copy link
Copy Markdown
Member

Problem

The interactive releaser (scripts/releaser) renders the "Latest Release"
cell of the release calendar with a doubled version prefix, e.g.
[vv2.35.0](.../tag/v2.35.0).

version.String() already returns a v-prefixed string (e.g. v2.35.0),
but updateCalendar wrapped it in a "[v%s]" template, so the link label
gained a second v. The tag URL was already correct because release tags
carry the v prefix.

Fix

Drop the extra v from the label template ("[v%s]""[%s]"). The URL is
unchanged.

  • Label before: [vv2.35.0]
  • Label after: [v2.35.0]

Test

Added scripts/releaser/docs_test.go:

  • TestUpdateCalendarLatestReleaseVersionPrefix asserts the LatestRelease
    cell for a matching row on both a patch and a minor release. It fails on the
    old code ([vv2.35.x]) and passes with the fix.
  • TestUpdateCalendarNotReleasedRowName covers the Not ReleasedMainline
    promotion and the major.minor "Release name" link (patch omitted).
Investigation notes

This PR was generated by Coder Agents.

@mtojek
mtojek requested a review from johnstcn July 15, 2026 10:58
@mtojek
mtojek marked this pull request as ready for review July 15, 2026 10:58
@mtojek
mtojek enabled auto-merge (squash) July 15, 2026 10:58
@mtojek
mtojek merged commit 744439f into release/2.34 Jul 15, 2026
52 of 53 checks passed
@mtojek
mtojek deleted the fix/release-calendar-doubled-version-prefix-2.34 branch July 15, 2026 10:59
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 15, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants