Skip to content

Put the latest tag into the env.version that the version-up title reads - #9443

Merged
yegor256 merged 2 commits into
objectionary:masterfrom
Thayorns:9349
Oct 15, 2026
Merged

yegor256 merged 2 commits into
objectionary:masterfrom
Thayorns:9349

Conversation

@Thayorns

Copy link
Copy Markdown
Contributor

up.yml computed the latest tag into a shell variable latest and exported it, which lives only as long as that one run step. The next step reads env.version, which nothing ever set, so every commit and pull request the workflow made said New version in README, with two spaces and no version, as in #9082 and #8310.

The step now writes the tag to $GITHUB_ENV as version, so the commit and the title read New version 0.63.2 in README. The sed that bumps the README still uses the shell variable, as before.

Closes #9349

@Thayorns

Copy link
Copy Markdown
Contributor Author

@yegor256 take a look please, happy to clarify why the export did not reach the next step.

@github-actions github-actions Bot added the core label Oct 12, 2026
@sonarqubecloud

Copy link
Copy Markdown

Copy link
Copy Markdown
Member

@Thayorns thanks for the patch. The change touches a release workflow and has no test, so I cannot verify that the title of the pull request now picks up env.version. I am leaving it to the maintainer to confirm.


Generated by Claude Code

@yegor256 yegor256 self-assigned this Oct 14, 2026
@yegor256
yegor256 merged commit f6c19d5 into objectionary:master Oct 15, 2026

Copy link
Copy Markdown
Member

@Thayorns thank you for the fix, merged: the version-up workflow now sets env.version.

Written by Claude Code Opus 5.5


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

up.yml opens pull requests titled "New version in README", because env.version is never set

2 participants