Conversation
The "Version to release" workflow_dispatch input now shows an example (1.2.3), making it clear the version must be entered without a "v" prefix. The workflow prepends "v" itself when tagging, so a "v"-prefixed input would produce a "vv1.2.3" tag and break the release-notes file lookup. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
amfelso
approved these changes
Jun 18, 2026
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
2 participants
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.
Summary
Clarifies the
Version to releaseinput on the Manual Prepare Release workflow (release-to-main.yml) so it's obvious the version must be entered without avprefix.Why
The workflow prepends the
vitself when tagging and cutting the GitHub release:git tag -a "v${{ ... version }}"tag_name: v${{ ... version }}…and uses the bare version for the release-notes file lookup (
helm/docs/releases/<version>.md). Enteringv1.2.3would therefore produce avv1.2.3tag and fail the release-notes check.workflow_dispatchinputs have no separate help/hint field, so the guidance lives in thedescriptiontext.