Skip to content

fix(release): suppress component prefix in release-please tags#166

Merged
zeitlinger merged 2 commits intomainfrom
fix/release-please-no-component-prefix
Apr 13, 2026
Merged

fix(release): suppress component prefix in release-please tags#166
zeitlinger merged 2 commits intomainfrom
fix/release-please-no-component-prefix

Conversation

@zeitlinger
Copy link
Copy Markdown
Member

Summary

  • Adds "include-component-in-tag": false to release-please config
  • Fixes tags being created as flint-v0.20.0 instead of v0.20.0
  • The release workflow triggers on v* — without this fix, it never fires

Context

The packages: { ".": ... } config causes release-please to prefix tags with the component name (flint-). Setting include-component-in-tag: false restores the plain v0.x.x format used by all prior releases (v0.9.x and earlier).

For v0.20.0, the tag was pushed manually as v0.20.0 to unblock the release workflow.

Add include-component-in-tag: false so release-please creates v0.x.x
tags instead of flint-v0.x.x, matching the release workflow trigger.
Set indentStyle=space/indentWidth=2 in biome.json and reformat all
tab-indented JSON files to match.
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
zeitlinger added a commit that referenced this pull request Apr 13, 2026
)

## Summary

- Adds `workflow_dispatch` trigger with a `tag` input to the release
workflow
- Passes the tag as `ref` to both `actions/checkout` and
`upload-rust-binary-action` (via `GITHUB_REF` override)
- No change to the normal push-triggered flow

## Why

The `v0.20.0` release workflow failed because the tag was
`flint-v0.20.0` (release-please bug, fixed in #166) and the release had
to be created manually. Due to tag protection rules and the
immutable-releases policy, there was no way to retrigger the workflow.
This adds an escape hatch for that situation.

---------

Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
@zeitlinger zeitlinger marked this pull request as ready for review April 13, 2026 16:16
@zeitlinger zeitlinger requested a review from a team as a code owner April 13, 2026 16:16
Copilot AI review requested due to automatic review settings April 13, 2026 16:16
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

Updates release automation configuration so release-please produces plain vX.Y.Z tags (without a component prefix), ensuring the existing release workflow (triggered by v* tags) fires correctly.

Changes:

  • Set include-component-in-tag: false in release-please config to stop generating flint-vX.Y.Z tags.
  • Reformat several JSON config files (tabs → 2-space indentation) and add Biome formatter settings to standardize formatting.

Reviewed changes

Copilot reviewed 2 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
.github/config/release-please-config.json Configures release-please to generate non-component-prefixed tags.
.github/config/.release-please-manifest.json Formatting-only update.
biome.json Adds formatter settings and reformats existing config for consistent JSON formatting.
default.json Formatting-only update to Renovate config.
.markdownlint.json Formatting-only update.

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

Comment thread biome.json
@zeitlinger zeitlinger merged commit 949fbf1 into main Apr 13, 2026
17 checks passed
@zeitlinger zeitlinger deleted the fix/release-please-no-component-prefix branch April 13, 2026 16:21
This was referenced Apr 13, 2026
zeitlinger added a commit that referenced this pull request Apr 16, 2026
### Added

- *(release)* migrate from release-please to release-plz
([#171](#171))

### Fixed

- *(release)* use correct template variable in pr_body
([#178](#178))
- *(release)* suppress component prefix in release-please tags
([#166](#166))
- *(release)* add workflow_dispatch to retrigger for existing tags
([#167](#167))

### Other

- move icon to assets/ to fix release-plz
([#177](#177))
- *(deps)* update dependency npm:renovate to v43.102.11 [security]
([#174](#174))
- *(deps)* update rust crate similar to v3.1.0
([#173](#173))
- *(deps)* update dependency github:mvdan/sh to v3.13.1
([#163](#163))

> [!IMPORTANT]
> Close and reopen this PR to trigger CI checks.

---------

Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
This was referenced Apr 16, 2026
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.

3 participants