chore: pin webware-tools to the released 1.0.0-beta.2 - #21
Merged
Merged
Conversation
Moves the dev-dependency off the 0.1.x dev branch now that the tooling has releases. beta.2 carries the mago 1.49.0 bump, so the vendored mago.toml matches the version the CI workflow installs. The caret floor lets beta.3, RC and 1.0.0 satisfy it without a re-pin. Signed-off-by: Joey Smith <jsmith@webinertia.net>
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
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.
What
Moves the
webware/webware-toolsdev-dependency off the^0.1.x-devbranch constraint and onto the released line:^1.0.0-beta.2.Why
The tooling now has releases to pin to. A branch constraint resolves to whatever the branch tip happens to be at install time; a version constraint is auditable, reproducible, and Renovate can track it.
1.0.0-beta.2is the first release carrying the mago 1.49.0 bump, so the vendoredmago.tomldeclares the same version the CI workflow installs — the version-drift warning that currently fires on every run goes away.The constraint carries a beta floor, so
beta.3, RC and1.0.0all satisfy it and no re-pin is needed as the cycle advances.Scope
composer.json(one line) plus the regeneratedcomposer.lock. No source, config or workflow changes.