Skip to content

chore: Use slash tag separator so Dependabot updates each action separately - #137

Open
jsonbailey wants to merge 1 commit into
mainfrom
jb/slash-tag-separator
Open

jsonbailey wants to merge 1 commit into
mainfrom
jb/slash-tag-separator

Conversation

@jsonbailey

@jsonbailey jsonbailey commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Dependabot treats every action in this repo as one dependency when the tags use a dash between the component and the version. It then rewrites every launchdarkly/gh-actions ref to the newest tag in the repo, which is often a tag for a different action. Example: hello-openfeature-java-server#24 moves verify-hello-app@verify-hello-app-v2.0.2 to verify-hello-app@release-secrets-v1.2.2. When the newest tag in the repo is older than an action's own latest release, this is a downgrade.

GitHub documents this limitation and recommends slash tags for monorepos (docs). A fix for dash tags in dependabot-core is still open (dependabot-core#15674).

  • Set tag-separator to /, so new releases are tagged like verify-hello-app/v2.0.3.
  • The major-tag step now pushes both <component>/v<major> and the existing <component>-v<major>, so consumers that pin the floating dash tags keep getting updates.

A release-please dry run on this branch finds all 10 current releases from their existing dash tags and opens no release PRs, the same as main. Existing tags stay as they are.

Follow-up: consumer repos must move their refs to slash tags once one exists for each action, because Dependabot does not change the tag format for them. Until then, consumers keep getting the bad PRs.


Note

Overview
Release Please now uses a / tag separator, so new action releases are named like verify-hello-app/v2.0.3 instead of dash-separated tags. That matches GitHub’s guidance for monorepos so Dependabot can bump each action ref independently instead of picking whichever tag is newest repo-wide.

The release workflow was updated to parse component names from slash-style full tags and to maintain two floating major refs on each release: component/v{major} and the legacy component-v{major}. Downstream repos that still pin dash major tags keep receiving updates while slash tags become available for migration.

Reviewed by Cursor Bugbot for commit 00ca70d. Bugbot is set up for automated code reviews on this repo. Configure here.

@jsonbailey
jsonbailey requested a review from keelerm84 November 21, 2026 00:01
@jsonbailey
jsonbailey marked this pull request as ready for review November 21, 2026 00:14
@jsonbailey
jsonbailey requested a review from a team as a code owner November 21, 2026 00:14
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