Repository navigation
chore: Use slash tag separator so Dependabot updates each action separately - #137
Open
jsonbailey wants to merge 1 commit into
Open
jsonbailey wants to merge 1 commit into
jsonbailey wants to merge 1 commit into
Conversation
jsonbailey
marked this pull request as ready for review
November 21, 2026 00:14
This was referenced Nov 21, 2026
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
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
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-actionsref to the newest tag in the repo, which is often a tag for a different action. Example: hello-openfeature-java-server#24 movesverify-hello-app@verify-hello-app-v2.0.2toverify-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).
tag-separatorto/, so new releases are tagged likeverify-hello-app/v2.0.3.<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 likeverify-hello-app/v2.0.3instead 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 legacycomponent-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.