chore: publish packages to NetBird repositories - #25
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe GoReleaser configuration separates Debian and RPM packages with format-specific dependencies, payloads, scripts, and upload targets. CI supplies separate upload variables, while README and reference documentation describe APT/YUM repository installation and upgrades. ChangesPackage split and documentation update
Estimated code review effort: 3 (Moderate) | ~20 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 @.goreleaser.yml:
- Around line 247-258: The archive upload targets in the goreleaser config are
templating architecture from values that are empty in archive mode, so fix the
Debian and yum upload entries to use explicit architecture values instead of
`.Arch`/`.Arm`. Update the affected release targets in the archive upload
section so the Debian `deb.architecture` and yum path resolve to the intended
fixed architectures, or change the upload mode only if dynamic templating is
actually required.
In `@README.md`:
- Around line 27-64: The README repository install instructions use the wrong
package domain, so update the APT and YUM URLs in the documented install steps
to match the actual GoReleaser upload targets used for the package artifacts.
Check the repository install sections that mention `pkgs.netbird.io` and align
them with the canonical domain used by the release pipeline (or adjust the
release config if that domain is intended), so the `curl`, `deb`, and `repo`
references all point to the same host.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: e5a3f6df-b469-40bd-86d0-64502e59ba66
📒 Files selected for processing (4)
.github/workflows/release.yml.goreleaser.ymlREADME.mddocs/reference.md
Description
.deband.rpmrelease artifacts to the NetBird APT/YUM repositories from GoReleaser.Validation
task quality:fullfor risky changes (not run locally)go test ./...git diff --checkSummary by CodeRabbit
Summary by CodeRabbit
New Features
Documentation
network-manager-netbirdAPT/YUM packages.Build/Release