Repository navigation
fix: pin packages to 0.1.0 - #106
Merged
Merged
Conversation
release-please's dart updater rewrites pubspec.yaml through a YAML round-trip, which strips the x-release-please-version marker on the plugin_source constraint. The release PR then bumped plugin_source to 0.2.0 while the CLI still required ^0.1.0, and workspace resolution failed in every job that runs dart pub get. Follow mason_cli's approach instead: a hosted range that survives the linked 0.x bumps, with the workspace supplying the local package. The generic updater now only touches lib/src/version.dart. Also ignore the CHANGELOG compare links in lychee, since the tags they point at only exist once the release PR merges.
The manifest already records 0.1.0, but nothing has been tagged or published yet, so release-please treated 0.1.0 as shipped and bumped the first release to 0.2.0. release-as pins the first release of both linked components to 0.1.0.
release-please writes the 0.1.0 entry from the commit history, and would otherwise prepend it above these, leaving two 0.1.0 sections.
marcossevilla
changed the title
With linked versions, every feat: bumped plugin_source's minor in 0.x and fell outside the CLI's ^0.1.0 constraint. Bumping the patch for features and fixes until 1.0, as mason does, keeps ^0.1.0 satisfied, so the CLI can go back to it. A breaking change bumps the minor and needs the constraint raised by hand on its release PR.
marcossevilla
changed the title
omartinma
approved these changes
Oct 29, 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.
Fixes the failing checks on #105.
Why #105 fails
dart pub getfails in bothbuildjobs,verify-pinsandlicense_check:plugin_sourcewas bumped to0.2.0while the CLI still required^0.1.0. Thex-release-please-versionmarker meant to bump that constraint was lost because release-please'sdartupdater rewritespubspec.yamlthrough a YAML round-trip, which strips comments.check_linksfails on the CHANGELOG compare links: their tags only exist once the release PR merges.0.2.0, not0.1.0: the manifest records0.1.0, so release-please treated it as already shipped even though nothing was tagged or published.Changes
plugin_source: ^0.1.0with no marker, the waymason_clidepends onmason, and setbump-minor-pre-majorandbump-patch-for-minor-pre-majorso that before 1.0 features and fixes bump the patch and stay inside^0.1.0. A breaking change bumps the minor and needs the constraint raised by hand on its release PR. The generic updater now only toucheslib/src/version.dart.vgv_ai_cli/compare/links in.lycheeignore.release-as: 0.1.0. Tracked for removal after 0.1.0 is published in chore: remove release-as after 0.1.0 is published #107, with a reminder comment inrelease_please.yaml.AGENTS.mdto match.