Skip to content

chore(main): release 0.0.0 - #43

Merged
vinzenzmay merged 2 commits into
mainfrom
release-please--branches--main--components--svirlpool
Jan 7, 2026
Merged

chore(main): release 0.0.0#43
vinzenzmay merged 2 commits into
mainfrom
release-please--branches--main--components--svirlpool

Conversation

@varfish-bot

@varfish-bot varfish-bot commented Dec 21, 2025

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.0.0 (2025-12-21)

Features

Bug Fixes

  • allowed mismatching chr names in mononucleotide filtering for re… (#30) (3821344)
  • HG30 sv calling feasible due to performance gains (#28) (6d9ae6c)

Documentation

Continuous Integration


This PR was generated with Release Please. See documentation.

@varfish-bot varfish-bot changed the title chore(main): release 0.0.1 chore(main): release 0.0.0 Dec 21, 2025
@varfish-bot
varfish-bot force-pushed the release-please--branches--main--components--svirlpool branch from f5bbb0a to 0e60a3e Compare December 21, 2025 21:24
@varfish-bot
varfish-bot force-pushed the release-please--branches--main--components--svirlpool branch from e086b49 to 1788748 Compare December 21, 2025 21:26
@holtgrewe

Copy link
Copy Markdown
Member

@vinzenzmay OK this should be live now as well. Once you merge this PR, it will create a version, release, and appropriately tagged Docker image is tagged. Just append a line Release-As: 0.1.0 to any commit in main (e.g., the merge commit message on merging a PR) to force-set version of next release to 0.1.0 etc.

@vinzenzmay
vinzenzmay merged commit 6833872 into main Jan 7, 2026
6 checks passed
@vinzenzmay
vinzenzmay deleted the release-please--branches--main--components--svirlpool branch January 7, 2026 10:56
@varfish-bot

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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.

3 participants