Skip to content

ci: fix incorrect naming in release tags#41

Merged
jkongie merged 1 commit intomainfrom
fix-release-tagging
May 6, 2026
Merged

ci: fix incorrect naming in release tags#41
jkongie merged 1 commit intomainfrom
fix-release-tagging

Conversation

@jkongie
Copy link
Copy Markdown
Collaborator

@jkongie jkongie commented May 6, 2026

This removes the repository name prefixed in the tag name. Go expects tags to be of the format v0.0.0 for module resolution.

This removes the repository name prefixed in the tag name. Go expects
tags to be of the format v0.0.0 for module resolution.
@jkongie jkongie requested a review from a team as a code owner May 6, 2026 14:44
Copilot AI review requested due to automatic review settings May 6, 2026 14:44
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

👋 jkongie, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Release Please configuration to stop prefixing release tags with the component/package name, aligning generated tags with Go module expectations (e.g., v0.1.0) for module resolution.

Changes:

  • Disable component-prefixed tag generation by setting include-component-in-tag to false for the root Go package.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@jkongie jkongie merged commit 778d6b7 into main May 6, 2026
17 checks passed
@jkongie jkongie deleted the fix-release-tagging branch May 6, 2026 15:15
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.

6 participants