Update docs on AI bundle: clarify GitHub release assets are static, update Quick Start to use container#3268
Merged
matthewhelmke merged 2 commits intochainguard-dev:mainfrom Apr 23, 2026
Conversation
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Collaborator
Author
|
Added a commit that updates places where static (outdated) files were being used with clarifying notes. |
s-stumbo
approved these changes
Apr 23, 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.
Summary
command, which pulls from the live container image
Preview: https://deploy-preview-3268--ornate-narwhal-088216.netlify.app/developer-resources/#download-options
Context
The ai-docs-bundle GitHub Release is covered by an org ruleset that makes release assets immutable. The workflow attempts to update them on each build but fails silently (the step has continue-on-error: true), meaning users who download from the release get stale documentation. The container (ghcr.io/chainguard-dev/ai-docs:latest) is updated correctly on each build and is the right path for current docs.
This PR updates the page to reflect that reality while a longer-term fix for the release update workflow is
investigated.