fix(ci): skip goreleaser validate pipe for prefixed tags#577
Merged
tolzhabayev merged 1 commit intomainfrom May 8, 2026
Merged
fix(ci): skip goreleaser validate pipe for prefixed tags#577tolzhabayev merged 1 commit intomainfrom
tolzhabayev merged 1 commit intomainfrom
Conversation
The previous attempt set `release.tag` in the goreleaser configs to map
the bare-semver override back to the prefixed git tag, but `release.tag`
is a GoReleaser Pro field and is rejected by the OSS schema:
yaml: unmarshal errors:
line 40: field tag not found in type config.Release
Revert to passing the full prefixed tag through GORELEASER_CURRENT_TAG
and bypassing the offending pipe with `--skip=validate`. Mirrors the
working pattern already used in the MCP workflow.
academo
approved these changes
May 8, 2026
github-project-automation
Bot
moved this from 📬 Triage
to 🔬 In review
in Grafana Catalog Team
github-project-automation
Bot
moved this from 🔬 In review
to 🚀 Shipped
in Grafana Catalog Team
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
Replaces the
release.tagconfig knob (which only exists in GoReleaser Pro) with--skip=validate, the same pattern the MCP workflow already uses. Also keepsGORELEASER_CURRENT_TAG: \${{ github.ref_name }}so the GitHub release goes to the right (prefixed) tag.Why
PR #575 tried to keep validation on by setting
release.tag: "plugin-validator/v{{ .Version }}"in the goreleaser configs. That field isn't in the OSS schema, so v2.15.4 rejects it:```
yaml: unmarshal errors:
line 40: field tag not found in type config.Release
```
Failed run after #575 merged
--skip=validateskips the validate pipe (semver parse, working-tree check, template validation) but in a post-tag-push CI run those checks aren't really protecting us — fresh checkout, known-good tag.Test plan