Open
Conversation
nhynes
force-pushed
the
nhynes/use-new-amber
branch
from
1d3dffb to
64d6100
Compare
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.
This PR updates the gateway in a mostly backwards-compatible way to use the latest amber. In particular removing the need for callback URLs (regular a2a card rewriting is still required due to a2a sdk defaults).
This PR also runs the tests in CI and bumps the github actions versions for the publish workflow.
To deploy this change with a minimum of breakage in the ecosystem, we will want to update the amber version used by the agentbeats CI workflow and merge this PR at about the same time. Existing manifests are pointing at the agentbeats-gateway manifest on the main branch (we should version it), so it means that all manifests will start pointing to this new version. This new version needs amber ≥v0.3.0, so we will need to update the CI workflow.
The
green_mcpslot andcallback_urlsconfig item are retained to prevent breakage.