Skip to content

v0.8.1#249

Merged
danielroe merged 2 commits into
mainfrom
release/v0.8.1
Jul 7, 2026
Merged

v0.8.1#249
danielroe merged 2 commits into
mainfrom
release/v0.8.1

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

v0.9.0 is the next minor release.

👉 Changelog

compare changes

🚀 Enhancements

📦 Build

  • migrate from unbuild to tsdown (5e1e90b)

🏡 Chore

✅ Tests

🤖 CI

❤️ Contributors

@Gerbuuun Gerbuuun mentioned this pull request Jul 7, 2026
@Gerbuuun

Gerbuuun commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

Closing in favor of #262. The unreleased changes include the Zero v1.4 dependency bump, so this should ship as v0.9.0 rather than v0.8.1.

@Gerbuuun Gerbuuun closed this Jul 7, 2026
@danielroe

Copy link
Copy Markdown
Owner

@Gerbuuun if we want to force a major version bump we need to do that with conventional commits, which will trigger an automatic PR being created

@Gerbuuun Gerbuuun reopened this Jul 7, 2026
@Gerbuuun Gerbuuun marked this pull request as ready for review July 7, 2026 10:44
@Gerbuuun

Gerbuuun commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

My agent was a bit too eager to release 🥴

So, a breaking change needs a ! in the commit?
I think releasing v0.8.1 is valid. Who needs to approve the commit? Does it do it automatically? I don't have access
@danielroe

@danielroe

Copy link
Copy Markdown
Owner

yikes.

@danielroe danielroe merged commit 2032235 into main Jul 7, 2026
8 checks passed
@danielroe danielroe deleted the release/v0.8.1 branch July 7, 2026 10:56
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