Update extensions spec#612
Open
jcarter3 wants to merge 1 commit into
Open
Conversation
jcarter3
requested review from
dmcgowan,
jdolitsky,
jonjohnsonjr,
jzelinskie,
mikebrow,
stevvooe and
sudo-bmitch
as code owners
sudo-bmitch
requested changes
May 21, 2026
Contributor
sudo-bmitch
left a comment
sudo-bmitch
left a comment
There was a problem hiding this comment.
DCO sign-off is also needed.
jcarter3
force-pushed
the
relax-extension-language
branch
2 times, most recently
from
09e7b49 to
8d6ac35
Compare
Contributor
|
From today's meeting: we need to document the requirement for a |
Signed-off-by: Jeff Carter <jeff.carter@docker.com>
jcarter3
force-pushed
the
relax-extension-language
branch
from
8d6ac35 to
0749538
Compare
sudo-bmitch
approved these changes
May 26, 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.
Update extensions spec to use relaxed language around route definition. The current language requires an extension to use and segments, and pass required dynamic values via query parameter.
This change loosens the requirements and leaves API design up to the extension itself, with the only requirement being that the routes do not clash.
Prior implementation: https://edu.chainguard.dev/chainguard/chainguard-images/features/using-the-tag-history-api/#calling-the-api