Tweak release.yml

[ciscorn]

Summary by CodeRabbit

• Chores
  • Updated the GitHub Actions workflow for more streamlined Rye environment handling and PyPI publishing.
• Refactor
  • Removed Pyright type-checking from the test workflow for efficiency.

[coderabbitai]

Walkthrough

The recent updates streamline the workflow for releasing and testing software. By integrating the Rye environment directly into the GitHub Path, the release process simplifies the setup steps, making the build process more straightforward. Additionally, the renaming of the publishing step clarifies its purpose. On the testing front, the removal of the Pyright type-checking step could indicate a shift in how code quality and type safety are managed, potentially relying on alternative methods or tools.

Changes

Files	Change Summary
.github/workflows/release.yml	Rye environment path appended to $GITHUB_PATH, simplified build step, renamed PyPI publishing step
.github/workflows/test.yml	Removed Pyright type-checking step

🐇✨
In the world of code, where rabbits dwell,
Changes come, ringing the bell.
Paths now clear, and steps now light,
No Pyright checks in the night.
To PyPI we go, with names so bright,
In workflows' dance, our code takes flight.
🚀🌟

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.61%. Comparing base (13e9759) to head (91d4e15).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage   98.61%   98.61%           
=======================================
  Files           2        2           
  Lines         506      506           
=======================================
  Hits          499      499           
  Misses          7        7           

Flag	Coverage Δ
unittests	98.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 13e9759 and 91d4e15.

Files selected for processing (2)

• .github/workflows/release.yml (1 hunks)
• .github/workflows/test.yml (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/test.yml

Additional comments: 3

.github/workflows/release.yml (3)

• 17-19: The addition of the Rye environment path to $GITHUB_PATH is a significant improvement. This change simplifies the workflow by automating the setup process, reducing the need for manual intervention and potential errors. However, ensure that the Rye environment setup script (curl -sSf https://rye-up.com/get | RYE_INSTALL_OPTION="--yes" bash) is trusted and secure, as executing scripts from the internet can pose security risks.
• 22-22: Automating the build process by directly calling rye build without explicitly sourcing the Rye environment is a streamlined approach, thanks to the previous step of appending the Rye environment path to $GITHUB_PATH. This change should make the workflow more efficient and less prone to errors. Just ensure that all necessary environment variables and paths are correctly set up by the Rye environment for the build process to succeed.
• 24-24: Renaming the publishing step to "Publish to PyPI" improves clarity and makes the workflow easier to understand at a glance. This change is a good practice for maintaining clear and descriptive names for workflow steps. No action is needed here unless there's a specific naming convention you're following that this change violates.