Skip to content

v0.0.71#117

Merged
Princesseuh merged 1 commit into
masterfrom
auto-version-bump
May 9, 2026
Merged

v0.0.71#117
Princesseuh merged 1 commit into
masterfrom
auto-version-bump

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Merge this PR to publish a new version. The version is determined by the PR title.

@johnsoncodehk johnsoncodehk marked this pull request as draft February 26, 2026 22:29
@github-actions github-actions Bot force-pushed the auto-version-bump branch 2 times, most recently from 12ea994 to fa3bae9 Compare March 4, 2026 14:22
@github-actions github-actions Bot force-pushed the auto-version-bump branch 3 times, most recently from 7b4be64 to 3f412bd Compare May 9, 2026 20:50
@github-actions github-actions Bot force-pushed the auto-version-bump branch from 3f412bd to 3c32ed3 Compare May 9, 2026 20:53
@johnsoncodehk
Copy link
Copy Markdown
Member

@Princesseuh, @remcohaszing It’s now possible to release this project without going through me. All that’s needed is to merge this PR directly. This is a great opportunity to give it a try.

@Princesseuh Princesseuh marked this pull request as ready for review May 9, 2026 23:43
@Princesseuh
Copy link
Copy Markdown
Member

Trying it!

@Princesseuh Princesseuh merged commit df36eeb into master May 9, 2026
@johnsoncodehk
Copy link
Copy Markdown
Member

johnsoncodehk commented May 9, 2026

It seems that since Squash Merging wasn’t used, the CI process didn’t trigger successfully. I just forced the push of the v0.0.71 commit to trigger the CI process again. I also changed the repository settings to enable Squash Merging only. Let’s continue to release updates in this manner from now on. The “Bus factor” of the repository is now 3. 🙌

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants