Skip to content

fix(network-ops): bump 3.0.0 -> 3.0.1 to unblock capability sync - #185

Merged
rdheekonda merged 1 commit into
mainfrom
fix/network-ops-sync-version-bump
Oct 19, 2026
Merged

rdheekonda merged 1 commit into
mainfrom
fix/network-ops-sync-version-bump

Conversation

@rdheekonda

Copy link
Copy Markdown
Contributor

Summary

The Sync Capabilities workflow on main is failing: Sync to staging and Sync to dev both error with

✗ network-ops: Client error '400 Bad Request' for url '.../dreadnode/network-ops/manifests/3.0.0'
Synced: 3 uploaded, 22 skipped, 1 failed

Root cause: published manifest versions are immutable, but network-ops content changed (f267209, report_item model fixes) without a version bump, so the sync tried to re-POST manifests/3.0.0 and got a 400. ai-red-teaming and the other 22 capabilities synced fine — only network-ops failed.

Fix: patch-bump network-ops 3.0.0 -> 3.0.1 so the updated manifest publishes cleanly.

Test plan

  • Only change is the version string; no behavioral change
  • On merge, the main Sync Capabilities run should upload network-ops 3.0.1 and go green

The sync to staging/dev failed with 400 POSTing manifests/3.0.0: published
manifest versions are immutable, but the last network-ops change (f267209,
report_item model fixes) altered content without bumping the version, so the
re-upload collided. Patch bump lets the new manifest publish.
@rdheekonda
rdheekonda merged commit f8089c9 into main Oct 19, 2026
4 checks passed
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.

1 participant