⬆️ Update eifinger/setup-rye action to v3 #759
Merged
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.
This PR contains the following updates:
v2.6.0
->v3.0.0
Release Notes
eifinger/setup-rye (eifinger/setup-rye)
v3.0.0
: 🌈 Faster default versionCompare Source
Faster default version
From this release on by default this action installs the
rye
version defined asdefault
inaction.yml
.This gets automatically updated in a new release of this action when a new version of rye is released.
If you don't want to wait for a new release of this action you can use use
version: latest
.The thoughts behind this change:
latest
. This will speed up self hosted runners and allows for further optimisation in the futurerye
. The only thing I have to do is validate the automatically created PR and merge it. This gives me the confidence that thedefault
version will never lack behind by more than a day.If you still want to always download the
latest
version of rye you have to change your config to:New rye releases will trigger a patch release
From this release on new releases of rye will trigger a patch release of this action. Before it always triggered a feature release.
Before:
2.1.0->2.2.0
Now:
2.1.0->2.1.1
🚨 Breaking changes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.