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.

Sign up for GitHub

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

Jump to bottom

chore(main): release 0.4.0 #229

Merged
merged 1 commit into from
Nov 20, 2024
Merged

chore(main): release 0.4.0 #229

merged 1 commit into from
Nov 20, 2024

Conversation

varfish-bot
Copy link
Contributor

@varfish-bot varfish-bot commented Nov 20, 2024 •
edited by coderabbitai bot
Loading

🤖 I have created a release beep boop

0.4.0 (2024-11-20)

Features

  • proper OpenAPI-documented and versioned endpoints (#227) (#228) (900858e)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • New Features

    • Introduced OpenAPI documentation and versioning for endpoints in version 0.4.0.

  • Bug Fixes

    • Resolved issues related to case-insensitive searches for OMIM terms and improved error handling in the /hpo/terms endpoint.

  • Documentation

    • Updated the changelog to reflect new version entries and features.

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Nov 20, 2024 •
edited
Loading

Walkthrough

The changes in this pull request involve updates to the CHANGELOG.md and Cargo.toml files for the viguno package. A new version entry for version 0.4.0 has been added to the changelog, detailing the introduction of OpenAPI documentation and versioning for endpoints. Additionally, the Cargo.toml file has been updated to reflect the new version number, changing from 0.3.2 to 0.4.0, and specifying the edition as 2021 while maintaining the existing dependencies.

Changes

File Change Summary
CHANGELOG.md Added new version entry for 0.4.0, detailing new features and previous version entries.
Cargo.toml Updated version from 0.3.2 to 0.4.0, specified edition as 2021, and confirmed dependency versions.

Poem

In the patch of code, a new version blooms,
With OpenAPI docs, it brightly looms.
From zero to four, we hop with glee,
Dependencies tidy, as happy as can be!
A changelog updated, our tale to tell,
In the garden of code, all's working well! 🐇✨

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 900858e and 78ce3b2.

⛔ 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 due to trivial changes (1)
  • Cargo.toml
🔇 Additional comments (2)
CHANGELOG.md (2)

3-4: LGTM! Version header follows the standard format.

The version header correctly follows the Keep a Changelog format with:

  • Proper semantic version number
  • GitHub compare URL between v0.3.2 and v0.4.0
  • Release date in YYYY-MM-DD format

6-8: LGTM! Feature entry is well-formatted and informative.

The feature entry follows conventional commits format and properly:

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>, 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.

@varfish-bot varfish-bot force-pushed the release-please--branches--main--components--varfish-org/viguno branch from 5459f86 to 78ce3b2 Compare November 20, 2024 13:02
@holtgrewe holtgrewe enabled auto-merge (squash) November 20, 2024 13:03
@holtgrewe holtgrewe merged commit a2f7647 into main Nov 20, 2024
11 checks passed
@holtgrewe holtgrewe deleted the release-please--branches--main--components--varfish-org/viguno branch November 20, 2024 13:07
@codecov Codecov
Copy link

codecov bot commented Nov 20, 2024 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.50%. Comparing base (900858e) to head (78ce3b2).
Report is 1 commits behind head on main.

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #229   +/-   ##
=======================================
  Coverage   68.50%   68.50%           
=======================================
  Files          13       13           
  Lines         962      962           
=======================================
  Hits          659      659           
  Misses        303      303

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

🚨 Try these New Features:

@varfish-bot
Copy link
Contributor Author

🤖 Release is at https://github.com/varfish-org/viguno/releases/tag/v0.4.0 🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
autorelease: tagged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@varfish-bot @holtgrewe