fix(web-security): bump to 1.6.0 to unblock dev capability sync - #117
Merged
Conversation
Three content changes landed on web-security since the 1.5.0 bump without a version bump: response-queue-poisoning skill (#116), tool-agnostic preflight guidance, and the pdtm preflight guard (CAP-1174). Re-publishing 1.5.0 with changed content 400s against dev (which already has 1.5.0 stored), failing the Sync Capabilities workflow. Bump to 1.6.0 so a fresh immutable version publishes cleanly across 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.
What
Bump
web-securitycapability version1.5.0->1.6.0.Why
The Sync Capabilities workflow (run 31614567028) failed on the Sync to dev job:
Root cause: three content changes landed on web-security after the last version bump (
d6919a6, which set 1.5.0) without bumping the version:6f80ddfadd response-queue-poisoning skill (Add response-queue-poisoning skill to web-security #116)53bec99tool-agnostic preflight guidance2cb04aepdtm preflight guard (CAP-1174)Dev already has an immutable
1.5.0stored, so re-publishing1.5.0with different content is rejected (400). Staging/prod succeeded only because they hadn't stored1.5.0yet — leaving envs inconsistent.Bumping to
1.6.0publishes a fresh immutable version cleanly across dev/staging/prod. Minor bump because a new skill (feature) was added.Test plan
web-securityuploads to dev/staging/prod without 400Create capability releasestagscapability/web-security/v1.6.0