Repository navigation
fix(ai-red-teaming): bump 1.20.0 -> 1.20.1 to unblock manifest sync - #200
Merged
Merged
Conversation
…t sync The Sync Capabilities workflow was failing with: ai-red-teaming: 409 Conflict: Capability version is immutable: dreadnode/ai-red-teaming@1.20.0 1.20.0 is already published and immutable, but its content changed after publish (PRs #195-#199: count corrections, parity test, white-box routing fix) without a version bump. Published versions are immutable, so the sync can't re-upload 1.20.0. Bump to 1.20.1 so the new content publishes cleanly to dev/staging/prod.
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
1 participant
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.
Problem
The Sync Capabilities workflow is red on
main(run 39545951818). One of the two failures is ai-red-teaming:1.20.0was published to the registry, then its content changed (PRs #195-#199: count fixes, parity test, white-box routing fix) without a version bump. Registry versions are immutable, so the sync can't re-upload1.20.0with new bytes.Fix
Bump
capability.yamlversion 1.20.0 -> 1.20.1 so the new content publishes cleanly to dev/staging/prod. (Same remedy as #185 for network-ops' earlier immutable-sync block.)Note - this PR does NOT fully green the workflow
The sync has a second, independent failure in
network-ops(different owner):network-ops' custom output item types (
host/user/credential/hash/share/weakness) are not registered in the item-type registry on any env (confirmed on dev: approved set isasset, attack_surface, finding, handoff, web_endpoint, web_vulnerability). That needs a platform-admin import+publish of those types on dev/staging/prod (the same pathattack_surface/handofftook) - tracked separately with the network-ops owners.