Repository navigation
chore: bump webware/webware-tools to 1.0.0-rc.5 - #98
Merged
Merged
Conversation
The constraint was pinned to 1.0.0-beta.2 by #77 in August and never moved, because the release wave that followed updated only the lock. A caret on beta.2 admits every later prerelease, so the lock resolved forward and the stale floor stayed invisible. Raising the floor to rc.5 matches traccio and makes the constraint honest. The caret still admits 1.0.0 stable and later. No lock version change: the lock already carried rc.5 from the maintenance PR, so only the content hash moves. The vendored tools were an install behind, which this update corrected.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
The
webware/webware-toolsconstraint was pinned to1.0.0-beta.2by #77 in August and never moved.Why it stayed stale
A caret on
beta.2admits every later prerelease, so^1.0.0-beta.2already satisfiedrc.3,rc.4, andrc.5. The release wave that followed therefore updated only the lock, and the stale floor stayed invisible. Nothing failed, because nothing had to move.Change
webware/webware-tools:^1.0.0-beta.2to^1.0.0-rc.5, matching traccio.The caret still admits
1.0.0stable and every later release, so this raises the floor without capping the ceiling.Diff
Two lines.
composer.lockcarries rc.5 already, so only the content hash moves:The update also corrected a stale vendor directory that was an install behind the lock.
Verification
composer install --dry-run: "Nothing to install, update or remove"composer why webware/webware-tools: resolves at^1.0.0-rc.5webware-tools/mago.tomlreportsversion = "1.55.0", the current pinmago format --check: already formattedmago lint,mago analyze,mago guard: no issuescomposer test: 100 tests, 179 assertions, OK