Skip to content

chore(main): release 2.0.1 - #30

Open
bitwise-fast-forward-merge[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

bitwise-fast-forward-merge[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@bitwise-fast-forward-merge

@bitwise-fast-forward-merge bitwise-fast-forward-merge Bot commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

2.0.1 (2026-09-08)

Bug Fixes

  • deps: update bitwise-media-group/github-workflows action to v6.2.0 (#29) (b2f0f29)
  • deps: update bitwise-media-group/github-workflows action to v6.3.0 (#32) (35faa27)

This PR was generated with Release Please. See documentation.

@bitwise-fast-forward-merge bitwise-fast-forward-merge Bot added the autorelease: pending A release is pending review label Aug 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Note

Merging this PR: this repository merges by fast-forward so every
commit keeps its original signature. The GitHub merge button is not used.
Once this PR is approved and all checks pass, a maintainer merges it by
commenting /merge on the PR.

The branch must be up to date with main (rebased and re-signed) to
fast-forward. If /merge reports it is not fast-forwardable, rebase onto
main and comment /merge again.

@bitwise-fast-forward-merge
bitwise-fast-forward-merge Bot force-pushed the release-please--branches--main branch 2 times, most recently from 73f0563 to edfa255 Compare September 7, 2026 20:43
@bitwise-fast-forward-merge
bitwise-fast-forward-merge Bot force-pushed the release-please--branches--main branch from edfa255 to 1ba37cf Compare September 8, 2026 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: pending A release is pending review

Projects

Status: New

Development

Successfully merging this pull request may close these issues.

0 participants