fix(release): use packages config to fix Release Please component mapping#15
Merged
Merged
Conversation
…ping
Root-level release-please config assigns component '' (empty) to bare
v{version} tags, which doesn't match the manifest key '.' (dot). This
causes Release Please to find Set(0) latest release SHAs and collect
zero commits, so no release PR is ever created after a feat: merge.
Moving to the packages format explicitly associates the '.' path with
bare version tags, fixing the component lookup.
…nent mapping" This reverts commit 4453f2e.
…ping
Root-level release-please config assigns component '' (empty) to bare
v{version} tags, which does not match the manifest key '.' (dot). This
causes Release Please to find Set(0) latest release SHAs and collect
zero commits, so no release PR is ever created after a feat: merge.
Moving to the packages format explicitly associates the '.' path with
bare version tags, fixing the component lookup.
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
1 participant
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.
Problem
Release Please has been silently producing no release PRs after
feat:commits land onmain. The logs show:Root cause: with root-level config (
release-typeat the top level), Release Please's tag parser assigns component''(empty string) to barev{version}tags. The manifest uses"."(dot) as the root package key. Since'' ≠ '.', all three existing tags (v0.1.0,v0.2.0,v0.3.0) are ignored, Release Please has no anchor SHA, collects zero commits, and creates nothing.Fix
Switch to the
packagesformat, which correctly maps the.path to bare version tags and matches the"."key in.release-please-manifest.json.{ "packages": { ".": { "release-type": "simple", "extra-files": ["gradle.properties"] } } }Test plan
feat:commit from PR feat: Google I/O 2026 dependency updates and new UX components #14 (0.3.0 → 0.4.0)