Releases: eifinger/setup-rye
v1.7.0 🌈 Add known checksums for rye 0.16.0
v1.6.0 🌈 Monorepo support
Changes
If your rye project is not at the root of the repository you can specify the working directory relative to the repository root. This is useful for monorepos.
If you do not use the caching feature working-directory
will have no effect.
- name: Enable caching and define a working directory
uses: eifinger/setup-rye@v1
with:
enable-cache: true
working-directory: 'path/to/rye/project'
Thank you @catwell for reporting this missing feature.
✨ New features
⬆️ Dependency updates
- chore(deps-dev): bump @types/node from 20.8.10 to 20.10.4 @dependabot (#111)
- chore(deps-dev): bump typescript from 5.2.2 to 5.3.3 @dependabot (#110)
- chore(deps-dev): bump eslint from 8.52.0 to 8.55.0 @dependabot (#108)
- chore(deps-dev): bump prettier from 3.0.3 to 3.1.0 @dependabot (#99)
- chore(deps-dev): bump @types/node from 20.8.9 to 20.8.10 @dependabot (#96)
v1.5.0 🌈 Fewer rate limits
Changes
🚀 Enhancements
- do not check releases for known versions @eifinger (#95)
- add known checksums for rye 0.15.2 @eifinger (#79)
⬆️ Dependency updates
- chore(deps-dev): bump eslint from 8.50.0 to 8.52.0 @dependabot (#90)
- chore(deps-dev): bump eslint-plugin-prettier from 5.0.0 to 5.0.1 @dependabot (#83)
- chore(deps): bump release-drafter/release-drafter from 5.24.0 to 5.25.0 @dependabot (#86)
- chore(deps): bump actions/setup-node from 3 to 4 @dependabot (#92)
- chore(deps-dev): bump @types/node from 20.8.2 to 20.8.9 @dependabot (#93)
- chore(deps-dev): bump eslint-plugin-jest from 27.4.2 to 27.6.0 @dependabot (#94)
v1.4.0 🌈 add known checksums for rye 0.15.0/0.15.1
v1.3.0 🌈 add known checksums for rye 0.14.0
v1.2.0 🌈 Automatically validate checksums of downloaded rye binaries
This action now automatically validates the checksum of the downloaded rye binary thus providing a new level of security.
Supported versions are currently 0.12.0
and 0.13.0
.
Until now you had to provide the checksum by yourself:
- name: Install a specific version and validate the checksum
uses: eifinger/setup-rye@v1
with:
version: '0.12.0'
checksum: 'c48d850e90649d868d512f60af67c74aa844d80f951fdb38589220662e709da7'
This option is still available and can be used should this action struggle to add known checksums for new rye releases in the future.
✨ New features
📚 Documentation
⬆️ Dependency updates
- chore(deps): bump actions/checkout from 3 to 4 @dependabot (#59)
- chore(deps-dev): bump prettier from 3.0.1 to 3.0.2 @dependabot (#44)
- chore(deps-dev): bump @types/node from 20.4.8 to 20.5.0 @dependabot (#43)
- chore(deps-dev): bump eslint from 8.46.0 to 8.47.0 @dependabot (#42)
- chore: bump versions @eifinger (#39)
- chore(deps-dev): bump prettier from 3.0.0 to 3.0.1 @dependabot (#35)
- chore(deps-dev): bump eslint-plugin-jest from 27.2.1 to 27.2.3 @dependabot (#33)
- chore(deps-dev): bump jest from 29.5.0 to 29.6.2 @dependabot (#32)
- chore(deps-dev): bump @typescript-eslint/parser from 5.59.2 to 5.62.0 @dependabot (#30)
v1.1.0 🌈 Speed up your builds
🚤 Caching
You can now opt-in to speed up your build by caching the .venv
directory.
Especially for large projects with many dependencies this can speed up runs a lot!
- name: Enable caching and define a custom cache key prefix
uses: eifinger/setup-rye@v1
with:
enable-cache: true
cache-prefix: 'optional-prefix'
This release also adds the support for arm64
(known in rye as aarch64) and x86
runners.
✨ New features
v1.0.5 🌈
v1.0.4 🌈 Python problem matchers
Initial Release of setup-rye
setup-rye
Set up your GitHub Actions workflow with a specific version of rye.
Limitations
Usage
- name: Checkout your repository
uses: actions/checkout@v3
- name: Install the latest version of rye
uses: eifinger/setup-rye@v1
- name: Sync your dependencies
run: rye sync
You can also specify a specific version of rye
- name: Install a specific version
uses: eifinger/setup-rye@v1
with:
version: '0.10.0'
How it works
This action downloads rye from the releases of the rye repo and uses the GitHub Actions Toolkit to cache it as a tool to speed up consecutive runs especially on self-hosted runners.
The installed version of rye is then added to the runner path so other steps can just use it by calling rye
.