Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: update classifiers #1

Merged
merged 1 commit into from
Jun 9, 2024
Merged

feat: update classifiers #1

merged 1 commit into from
Jun 9, 2024

Conversation

bdraco
Copy link
Member

@bdraco bdraco commented Jun 9, 2024

Summary by CodeRabbit

  • Chores
    • Updated project metadata to reflect stable development status and added support for Python versions 3.10, 3.11, and 3.12.

Copy link
Contributor

coderabbitai bot commented Jun 9, 2024

Walkthrough

The recent update to the pyproject.toml file focuses on revising the project metadata classifiers. It transitions the development status from pre-alpha to production/stable, enhances the project's categorization, and extends support to newer Python versions (3.10, 3.11, and 3.12).

Changes

Files Change Summary
pyproject.toml Updated classifiers: removed Development Status :: 2 - Pre-Alpha, added Development Status :: 5 - Production/Stable, Topic :: Software Development :: Build Tools, and Python version support for 3.10, 3.11, and 3.12.

Poem

In the code's grand tome, a shift we see,
From pre-alpha whispers to stable decree.
Python's new friends, 3.10 through 12,
Join the dance where innovations delve.
Build tools now take a central stage,
In the project's bright, evolving page.
🌟🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
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 testing code 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 testing code 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 testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @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.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@bdraco bdraco marked this pull request as ready for review June 9, 2024 18:09
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6bf66c2 and e15d763.

Files selected for processing (1)
  • pyproject.toml (1 hunks)
Additional comments not posted (1)
pyproject.toml (1)

15-19: Updated classifiers align well with the project's progression.

The addition of new Python versions and the change in development status reflect the project's growth and readiness for a wider audience. Ensure that all dependencies and the rest of the codebase are compatible with these new Python versions.

@bdraco bdraco merged commit 0d4eaf6 into main Jun 9, 2024
6 of 7 checks passed
@bdraco bdraco deleted the update_classifiers branch June 9, 2024 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant