chore(main): release 0.31.0

[varfish-bot]

🤖 I have created a release beep boop

0.31.0 (2025-01-30)

Features

• Add rare amino acid SO term (#658) (aee7693)
• refactor db subset CLI, add subset by VCF and subset by TxId options (#641) (9286286)

Bug Fixes

• Consolidate CLI (#650) (08c8fb6)
• ensure FORMAT sample order is in-sync with header sample order (#671) (1d3c230)
• include mehari cmd and version info in VCF header (#673) (8b9fa2e)
• inframe vs missense (#659) (36bd717)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features

  • Added a rare amino acid SO term
  • Enhanced database subset CLI with VCF and TxId subsetting options

• Bug Fixes

  • Consolidated CLI functionality
  • Synchronized FORMAT sample order with header sample order
  • Added mehari command and version information to VCF header
  • Clarified inframe and missense variant distinctions

• Chores

  • Updated package version to 0.31.0

[coderabbitai]

Walkthrough

The pull request introduces updates to the CHANGELOG.md and Cargo.toml files. A new version entry for version 0.31.0 has been added to the changelog, detailing the addition of a rare amino acid SO term and a refactor of the database subset command-line interface (CLI) to include new options for subsetting by VCF and TxId. The Cargo.toml file reflects the version increment from 0.30.1 to 0.31.0, indicating a new version of the package while maintaining the existing structure without changes to dependencies.

Changes

File	Change Summary
CHANGELOG.md	Added new version entry for version 0.31.0, detailing new CLI options for subsetting by VCF and TxId, and a bug fix for variant distinction.
Cargo.toml	Updated package version from 0.30.1 to 0.31.0; no changes to dependencies or configurations.

Possibly related PRs

• chore(main): release 0.30.1 #630: This PR introduces a new section in the CHANGELOG.md for version 0.30.1, which includes a bug fix related to the OpenAPI specification for the /api/v1/genes/transcripts endpoint, relevant to the changes made in the main PR that also updates the changelog and version number.
• fix: include mehari cmd and version info in VCF header #673: This PR enhances the VCF header by adding command and version information, which aligns with the main PR's focus on documenting version information in the changelog and VCF header.

Suggested labels

autorelease: tagged

Poem

In the meadow, changes bloom,
A version new dispels the gloom.
With options fresh for all to see,
The CLI dances, wild and free!
Hop along, let joy take flight,
For version 0.31 shines bright! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1a95ba9 and 37cd36c.

⛔ 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 (2)

• Cargo.toml
• CHANGELOG.md

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Schema
• GitHub Check: Testing
• GitHub Check: Linting
• GitHub Check: build-and-push-image

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CHANGELOG.md (1)

4-5: Remove extra empty lines.

Consider removing one of the two consecutive empty lines between sections to maintain consistent spacing throughout the changelog.

 ## [0.31.0](https://github.com/varfish-org/mehari/compare/v0.30.1...v0.31.0) (2025-01-24)
-
 
 ### Features
-
 
 * Add rare amino acid SO term ([#658](https://github.com/varfish-org/mehari/issues/658)) ([aee7693](https://github.com/varfish-org/mehari/commit/aee76930c633ab1be6fb023da042ca3fa1255ae4))

Also applies to: 10-11

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8ca1c80 and 1a95ba9.

⛔ 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

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Testing
• GitHub Check: Schema
• GitHub Check: build-and-push-image

🔇 Additional comments (2)

CHANGELOG.md (2)

3-16: LGTM! Well-structured version entry.

The new version entry follows the conventional changelog format with proper categorization, issue links, and commit hashes.

---

3-3: LGTM! Proper integration with existing entries.

The new version entry maintains chronological order and follows the same format as previous entries.

Also applies to: 17-17