Releases: eifinger/setup-rye
v4.0.1 🌈 update default version to 0.36.0
v4.0.0 🌈
This release fixes some issues that led to the creation and use of corrupted caches.
For reasons explained in #283 this action always saved the cache after each run. Now the cache is only uploaded when the whole run is a success which should prevent the upload of .venv which is not fully populated and/or corrupted.
Moreover after a successful cache restore we now check if the restored .venv was created in the exact same path as the current path. If this is not the case it can lead to undefined behavior as explained in #287. Therefore we now discard the cache in this case and do not set the cache-hit
output to true
.
Changes
🚨 Breaking changes
🐛 Bug fixes
- Check for wrong venv path in cache @eifinger (#287)
- Remove duplicate message on local cache miss @eifinger (#285)
- Overwrite the cached venv path in rye-venv.json @eifinger (#284)
- Only save cache when run succeeded @eifinger (#283)
🚀 Enhancements
⬆️ Dependency updates
v3.0.3 🌈 update default version to 0.35.0
Changes
🐛 Bug fixes
- chore: update default version to 0.35.0 @github-actions (#276)
⬆️ Dependency updates
- chore(deps-dev): bump prettier from 3.2.5 to 3.3.2 @dependabot (#264)
- chore(deps): bump peter-evans/create-pull-request from 6.0.5 to 6.1.0 @dependabot (#271)
v3.0.2 🌈 update default version to 0.34.0
v3.0.1 🌈 Set cache-hit to true if any cache key matched
Changes
In some cases the cache backend reported a mismatched cache key even though the cache was successfully restored. This is ignored now and a successfully restored cache will set the output cache-hit=true
🐛 Bug fixes
📚 Documentation
⬆️ Dependency updates
- chore(deps-dev): bump eslint and octokit-rest @dependabot (#236)
- chore(deps-dev): bump @types/node from 20.11.30 to 20.12.11 @dependabot (#240)
- chore(deps): bump peter-evans/create-pull-request from 6.0.2 to 6.0.5 @dependabot (#231)
- chore(deps-dev): bump typescript from 5.4.3 to 5.4.5 @dependabot (#227)
v3.0.0 🌈 Faster default version
Faster default version
From this release on by default this action installs the rye
version defined as default
in action.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:
- Since the default is now a static version this means by default the tools cache can be used instead of always downloading
latest
. This will speed up self hosted runners and allows for further optimisation in the future - I fully automated everything that needs to be done to incorporate a new version of
rye
. 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:
- name: Install a specific version
uses: eifinger/setup-rye@v3
with:
version: 'latest'
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
v2.6.0 🌈 add known checksums for 0.33.0
Changes
add known checksums for 0.33.0
🚀 Enhancements
- chore: add checksums for rye 0.33.0 @github-actions (#230)
v2.5.2 🌈 Fix restoring rye global settings
v2.5.1 🌈 add known checksums for 0.32.0
v2.5.0 🌈 Add known checksums for 0.31.0
Changes
🚀 Enhancements
- chore: add known checksums for 0.31.0 @github-actions (#213)
⬆️ Dependency updates
- chore(deps-dev): bump @types/node from 20.11.25 to 20.11.30 @dependabot (#211)
- chore(deps-dev): bump typescript from 5.4.2 to 5.4.3 @dependabot (#212)