Run Semantic Release in an environment with uv and npm installed #256
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 Python CLI for Semantic Release provides the exact same functionality as the GitHub Action. Running on the CI host with the CLI allows us to have uv and npm available, so the Semantic Release build step to update lockfiles is able to run. The
python-semantic-release versioncommand already has all the defaults to run the build step, make a commit, push a tag, and push a release (the same steps as before).This uses
uvxto ephimerally install Semantic Release, instead of adding it as a proper dependency, since the version of Click required by Semantic Release is old and unnecessarily constrains other packages. Developers are not expected to run Semantic Release themselves locally.