feat(netprobe): one-touch attribution + republish add-on on release (#3425) #3522

Merged

mfreeman451 merged 1 commit from feat/netprobe-one-touch-attribution into staging

2026-06-03 22:02:27 +00:00

mfreeman451 commented

2026-06-03 22:01:35 +00:00

Owner

native-addons.yml now triggers on v* release tags (was workflow_dispatch only),
so the netprobe add-on republishes on every release instead of being frozen at
0.1.0 regardless of code changes. Bump netprobe add-on 0.1.0 -> 0.2.0.
Enabling netprobe now runs the eBPF process-attribution path on its own:
netprobeConfigHasWork no longer requires capture_interfaces + device_bindings.
Attribution (the flow->process source behind attributed flows) needs no capture
config; capture/DPI stay additive opt-in. Schema text + defaults updated so
Enabled is the only required field.

Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com

IMPORTANT: Please sign the Developer Certificate of Origin

Thank you for your contribution to ServiceRadar. Please note, when contributing, the developer must include
a DCO sign-off statement indicating the DCO acceptance in one commit message. Here
is an example DCO Signed-off-by line in a commit message:

Signed-off-by: J. Doe <j.doe@domain.com>

Describe your changes

Issue ticket number and link

Code checklist before requesting a review

I have signed the DCO?
The build completes without errors?
All tests are passing when running make test?

- native-addons.yml now triggers on v* release tags (was workflow_dispatch only), so the netprobe add-on republishes on every release instead of being frozen at 0.1.0 regardless of code changes. Bump netprobe add-on 0.1.0 -> 0.2.0. - Enabling netprobe now runs the eBPF process-attribution path on its own: netprobeConfigHasWork no longer requires capture_interfaces + device_bindings. Attribution (the flow->process source behind attributed flows) needs no capture config; capture/DPI stay additive opt-in. Schema text + defaults updated so Enabled is the only required field. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> ## IMPORTANT: Please sign the Developer Certificate of Origin Thank you for your contribution to ServiceRadar. Please note, when contributing, the developer must include a [DCO sign-off statement]( https://developercertificate.org/) indicating the DCO acceptance in one commit message. Here is an example DCO Signed-off-by line in a commit message: ``` Signed-off-by: J. Doe <j.doe@domain.com> ``` ## Describe your changes ## Issue ticket number and link ## Code checklist before requesting a review - [ ] I have signed the DCO? - [ ] The build completes without errors? - [ ] All tests are passing when running make test?

Rows
Columns