chore(main): release 0.30.0

[varfish-bot]

🤖 I have created a release beep boop

0.30.0 (2024-11-20)

⚠ BREAKING CHANGES

• include source information in transcript database (#615)
• provide sub command "server run" (#600) (feat!: provide sub command "server run" (#600) #602)

Features

• /api/v1/seqvars/csq endpoint with OpenAPI (#606) (#614) (2fdf76e)
• /api/v1/strucvars/csq endpoint with OpenAPI (#607) (#612) (cce8a6d)
• provide genes/transcripts endpoint with openapi (#605) (#610) (9132312)
• provide sub command "server run" (#600) (#602) (48382b6)

Bug Fixes

• refactor csq analysis code (#599) (faffad6)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features

  • Introduced new API endpoints: /api/v1/seqvars/csq, /api/v1/strucvars/csq, and genes/transcripts with OpenAPI documentation.
  • Added the "server run" subcommand to the command-line interface.

• Breaking Changes

  • Source information is now required in the transcript database.

• Documentation

  • Updated changelog to reflect changes in version 0.30.0, including new features and breaking changes.

[coderabbitai]

Walkthrough

The pull request introduces version 0.30.0 for the mehari package, updating the CHANGELOG.md to document this release and its breaking changes, including the requirement to include source information in the transcript database and the addition of the "server run" subcommand to the command-line interface. The Cargo.toml file is also updated to reflect the new version number while maintaining the existing structure and dependencies.

Changes

File	Change Summary
CHANGELOG.md	Added new version entry for 0.30.0, detailing breaking changes and new features, including the "server run" subcommand and endpoints /api/v1/seqvars/csq, /api/v1/strucvars/csq, and "genes/transcripts" with OpenAPI documentation, referencing issues #600, #605, #606, #610, #612, and #614.
Cargo.toml	Updated version from 0.29.6 to 0.30.0; no changes to dependencies or other configurations.

Possibly related PRs

• chore: Update documentation to match current CLI/usage #595: This PR updates documentation related to the command-line interface, which includes the "server run" subcommand mentioned in the main PR.

Poem

🐰 In the meadow, changes bloom,
A new command dispels the gloom.
Version thirty, a leap we take,
With "server run," new paths we make.
Hopping forward, bright and free,
Celebrate with joy, come dance with me! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 008e380 and dcf203b.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• Cargo.toml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• Cargo.toml

🔇 Additional comments (3)

CHANGELOG.md (3)

3-5: LGTM! Version entry follows the standard format.

The version entry header is well-formatted with:

• Proper version number
• Link to version comparison
• Release date

---

6-10: Breaking changes are well documented.

Breaking changes are clearly identified and properly linked to their respective issues and PRs.

Please ensure that:

1. Documentation is updated to reflect the source information requirement in the transcript database
2. Users are notified about the new "server run" subcommand in upgrade guides

---

11-17: Features are well documented with proper references.

Each feature is properly documented with:

• Clear description
• Links to related issues and PRs
• Commit hashes for traceability

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.38%. Comparing base (ba15439) to head (92b80d2).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #603   +/-   ##
=======================================
  Coverage   73.38%   73.38%           
=======================================
  Files          28       28           
  Lines        9948     9948           
=======================================
  Hits         7300     7300           
  Misses       2648     2648           

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

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

CHANGELOG.md (1)

10-12: Consider if duplicate entries are necessary.

The feature entry duplicates the breaking change entry. While it's not incorrect to list a breaking change in both sections, consider if this duplication adds value or might cause confusion.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b4b743a and 92b80d2.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• Cargo.toml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• Cargo.toml

🔇 Additional comments (2)

CHANGELOG.md (2)

3-4: LGTM!

The version entry follows the conventional changelog format with proper GitHub compare URL and date formatting.

---

6-8: LGTM!

Breaking change is properly documented with clear references to the related issue and pull request.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

CHANGELOG.md (1)

3-17: LGTM! Well-structured changelog entry.

The changelog entry follows the conventional commit format, with proper sections for breaking changes and features. All changes are well-documented with issue/PR references and commit hashes.

Consider adding a migration guide section to help users handle the breaking changes:

• Database schema change for transcript source information
• CLI interface change with the new "server run" subcommand

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 66613c4 and 008e380.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• Cargo.toml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• Cargo.toml

[varfish-bot]

🤖 Created releases:

• v0.30.0
  🌻