Docs: Drop GitHub Releases from AI docs pipeline; redirect users#3288
Merged
matthewhelmke merged 1 commit intoApr 30, 2026
Merged
Docs: Drop GitHub Releases from AI docs pipeline; redirect users#3288matthewhelmke merged 1 commit into
matthewhelmke merged 1 commit into
Conversation
…er/MCP Immutable releases (org ruleset) made the cleanup step fail on every run, and the high dispatch frequency was accumulating releases without bound. GCS and the container are already the live distribution layer, so GitHub Releases were a redundant channel causing errors with no path to fix. - compile-ai-docs-from-gcs.yaml: remove Create Release and Clean Up Old Releases steps; move Sign step before GCS upload; add .bundle files to GCS upload; drop contents:write permission; remove release-related egress endpoints; remove dead create_release dispatch input - developer-resources.md: remove GitHub Release table row; update intro and standalone script link to point to MCP docs - mcp-server-ai-docs.md: replace release curl commands with raw.githubusercontent.com for scripts + container extract for docs - ai-docs-security.md: replace direct-download verification block with container image verification Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
s-stumbo
approved these changes
Apr 30, 2026
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
2 participants
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.
Drop GitHub Releases from AI docs pipeline; redirect users to container/MCP
Immutable releases (org ruleset) made the cleanup step fail on every run, and the high dispatch frequency was accumulating releases without bound. GCS and the container are already the live distribution layer, so GitHub Releases were a redundant channel causing errors with no path to fix.
Changes:
compile-ai-docs-from-gcs.yaml: remove Create Release and Clean Up Old Releases steps; move Sign step before GCS upload; add .bundle files to GCS upload; drop contents:write permission; remove release-related egress endpoints; remove dead create_release dispatch inputdeveloper-resources.md: remove GitHub Release table row; update intro and standalone script link to point to MCP docsmcp-server-ai-docs.md: replace release curl commands with raw.githubusercontent.com for scripts + container extract for docsai-docs-security.md: replace direct-download verification block with container image verificationFixes #3286 and
Fixes https://github.com/chainguard-dev/internal/issues/5823