Repository navigation
chore: prepare netbird v0.8.0 release - #157
Merged
Merged
Conversation
- Bump chart version 0.7.2 -> 0.8.0 - appVersion 0.82.0, dashboard image v2.96.0 - Refresh compatibility matrix: chart 0.8 verified against server 0.82.0, 0.81.5, 0.80.0, 0.79.0, 0.78.2 — all PASS Contains a breaking change (#156): database.type=mysql is rejected because NetBird 0.82.0 removed its MySQL store. Released as a minor rather than 1.0.0 because the chart is pre-1.0 (same as 0.7.0); migration steps are in CHANGELOG.md. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release netbird 0.8.0, covering #156:
feat!Removed: MySQL support. NetBird 0.82.0 removed its MySQL store; the chart now rejectsdatabase.type: mysqlat template time with the migration path.Compatibility matrix refreshed: chart 0.8 tested against server 0.82.0 / 0.81.5 / 0.80.0 / 0.79.0 / 0.78.2, all PASS.
The change is breaking (
!/BREAKING CHANGE), which the release skill would map to 1.0.0. As with 0.7.0, I'm releasing 0.8.0: the chart is pre-1.0, where SemVer treats the minor as the vehicle for breaking changes, and cutting 1.0.0 is a stability statement for you to make. The fail-fast error and the CHANGELOG migration steps protect MySQL users either way. Say the word and I'll retag as 1.0.0.MySQL users: stay on chart 0.7.x, migrate to PostgreSQL with
netbird-mysql-migratefrom v0.81.5, then upgrade. Details are inCHANGELOG.md.Merging this triggers the release workflow (GHCR OCI push,
netbird-0.8.0tag, GitHub release).How to verify
🤖 Generated with Claude Code