Bump netbird submodule to v0.72.3#195
Conversation
📝 WalkthroughWalkthroughThis PR advances the ChangesNetbird Submodule Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@netbird`:
- Line 1: The netbird submodule gitlink currently points to commit
d7703767d5f211fa41f516340e191b9e609e4f45 which does not correspond to the
v0.72.3 tag; locate the submodule entry for "netbird" (the gitlink/commit SHA in
the repo index or .gitmodules reference) and either update the gitlink to the
actual commit SHA that matches the intended v0.72.3 tag or retarget the
submodule to a real upstream tag (e.g., v0.72.2 or the correct v0.72.x tag) by
verifying the tag exists upstream and setting the gitlink to that tag's commit
SHA; commit the updated submodule reference so the repo points to a consistent,
existing release.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| @@ -1 +1 @@ | |||
| Subproject commit 07e5450117dd0451aaeefc18729a822115587e69 | |||
| Subproject commit d7703767d5f211fa41f516340e191b9e609e4f45 | |||
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify that the submodule commit hash corresponds to tag v0.72.3
cd netbird || exit 1
# Fetch latest tags
git fetch --tags origin
# Get the commit hash for tag v0.72.3
tag_commit=$(git rev-parse v0.72.3 2>/dev/null)
# The commit in the gitlink
expected_commit="d7703767d5f211fa41f516340e191b9e609e4f45"
echo "Expected commit (from gitlink): ${expected_commit}"
echo "Tag v0.72.3 points to: ${tag_commit}"
if [ "$tag_commit" = "$expected_commit" ]; then
echo "✓ Commit hash matches tag v0.72.3"
else
echo "✗ Mismatch: gitlink does not point to v0.72.3"
exit 1
fi
# Show tag details
git show v0.72.3 --no-patch --format="%H %s"Repository: netbirdio/android-client
Length of output: 1668
🌐 Web query:
netbird v0.72.3 release notes breaking changes
💡 Result:
As of June 10, 2026, NetBird has not released a version 0.72.3 [1][2]. The latest available releases are v0.72.0, v0.72.1, and v0.72.2 [1][3][4]. While there are no breaking changes associated with a non-existent v0.72.3, users upgrading to the v0.72.x series from earlier versions are required to make configuration changes if they are self-hosting with the built-in Traefik setup [5]. For those migrating to v0.72.x, the following manual updates are necessary [5]: 1. Update the gRPC router configuration: You must add the path prefix /management.ProxyService/ to the netbird-grpc.rule label in your docker-compose.yml file [5]. Example change: - traefik.http.routers.netbird-grpc.rule=Host(netbird.example.com) && (PathPrefix(/signalexchange.SignalExchange/) || PathPrefix(/management.ManagementService/) || PathPrefix(/management.ProxyService/)) 2. Optional Private Service Configuration: If you wish to support private services, you must manually add the following line to your proxy.env file [5]: NB_PROXY_PRIVATE=true After these updates, perform a standard redeployment: docker compose pull docker compose up -d
Citations:
- 1: https://github.com/netbirdio/netbird/releases
- 2: https://newreleases.io/project/github/netbirdio/netbird/release/v0.72.0
- 3: https://github.com/netbirdio/netbird/releases/tag/v0.72.2
- 4: https://github.com/netbirdio/netbird/releases/tag/v0.72.1
- 5: https://forum.netbird.io/t/migrating-to-v0-72-private-services-and-proxy-clusters/781
Fix the submodule bump target: gitlink d7703767… doesn’t correspond to v0.72.3
- The
netbirdgitlink is set tod7703767d5f211fa41f516340e191b9e609e4f45, but resolvingv0.72.3in the submodule does not point to that commit. - Upstream NetBird releases do not list a v0.72.3 (latest referenced 0.72.x releases are v0.72.0–v0.72.2), so the PR should verify the intended tag/commit (or retarget to the correct existing release).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@netbird` at line 1, The netbird submodule gitlink currently points to commit
d7703767d5f211fa41f516340e191b9e609e4f45 which does not correspond to the
v0.72.3 tag; locate the submodule entry for "netbird" (the gitlink/commit SHA in
the repo index or .gitmodules reference) and either update the gitlink to the
actual commit SHA that matches the intended v0.72.3 tag or retarget the
submodule to a real upstream tag (e.g., v0.72.2 or the correct v0.72.x tag) by
verifying the tag exists upstream and setting the gitlink to that tag's commit
SHA; commit the updated submodule reference so the repo points to a consistent,
existing release.
2 participants
Automated submodule bump triggered by netbird release v0.72.3.
Summary by CodeRabbit