Skip to content

Fix release workflow to use version for tag/release name#494

Open
runningcode wants to merge 2 commits intomasterfrom
no/fix-release-tag-name
Open

Fix release workflow to use version for tag/release name#494
runningcode wants to merge 2 commits intomasterfrom
no/fix-release-tag-name

Conversation

@runningcode
Copy link
Owner

Summary

  • When triggered via workflow_dispatch, the release and tag were named after the branch (e.g., master) instead of the actual version
  • Now extracts the version from fladle-plugin/build.gradle.kts and uses it for both the git tag and GitHub release name (e.g., v0.21.0)
  • Tag-triggered runs continue to work as before

🤖 Generated with Claude Code

runningcode and others added 2 commits March 14, 2026 10:27
When the release workflow is triggered via workflow_dispatch, the
release and tag were named after the branch (e.g., "master") instead of
the actual version. Now the version is extracted from build.gradle.kts
and used for both the tag and the GitHub release.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The workflow_dispatch trigger caused releases to be named after the
branch (e.g., "master") instead of the version. Since releases should
only be triggered by pushing a version tag, remove the manual trigger
entirely.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant