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

chore(main): release 0.4.0 #15

Merged

Conversation

varfish-bot
Copy link
Contributor

@varfish-bot varfish-bot commented Feb 7, 2024

🤖 I have created a release beep boop

0.4.0 (2024-02-07)

Features

Bug Fixes

  • pin cadd-scripts to 1.6-1 to increase stability (#14) (fa0c3d9)
  • strip chr prefix for grch38 (#10) (#11) (67be565)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • New Features

    • Introduced the setup of the release-please GitHub action for streamlined release management.
  • Bug Fixes

    • Pinned the cadd-scripts dependency to version 1.6-1 for improved stability.
    • Fixed an issue by stripping the "chr" prefix for the GRCh38 reference genome.

@holtgrewe holtgrewe enabled auto-merge (squash) June 10, 2024 12:44
@holtgrewe holtgrewe merged commit c7ab016 into main Dec 3, 2024
6 checks passed
@holtgrewe holtgrewe deleted the release-please--branches--main--components--cadd-rest-api branch December 3, 2024 13:16
@varfish-bot
Copy link
Contributor Author

Copy link

coderabbitai bot commented Dec 3, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates the CHANGELOG.md file to document the release of version 0.4.0 of the cadd-rest-api, which was released on February 7, 2024. It includes new features, such as the implementation of the release-please GitHub action, and addresses bug fixes related to dependency management and genome reference adjustments. No changes were made to the declarations of exported or public entities.

Changes

File Change Summary
CHANGELOG.md Updated to include details of version 0.4.0, featuring the release-please GitHub action and bug fixes for dependencies and genome reference.

Possibly related PRs

🐇 In the changelog, we now see,
Version 0.4.0, oh what glee!
With features bright and bugs all fixed,
Our code is neat, no longer mixed.
Hopping forth, we celebrate,
Stability's here, let's elevate! 🎉


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 043fdb8 and e21a5bb.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants