[AAASM-4773] 📝 (ci): Correct remaining stale gateway-image comments#327
Merged
Merged
Conversation
…live ghcr.io/ai-agent-assembly/aa-gateway is now published (tags v0.0.1-rc.4/rc.5/rc.6/latest), so the "not yet published"/"unpublished image" claims in scenarios/live-core-enforcement/docker-compose.yml and .github/workflows/verify-live.yml's header are stale. Companion to AAASM-4743 (README) and AAASM-4771 (verify-scenarios.yml job comment), which already corrected the same claim elsewhere. Comment-only; no trigger or runtime behavior changes. Refs AAASM-4773
|
Contributor
Author
Claude Code — automated reviewCI: all green (full scenario matrix); both YAML files parse. |
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 changed
ghcr.io/ai-agent-assembly/aa-gatewayis now published (tagsv0.0.1-rc.4/rc.5/rc.6/latest), but two remaining surfaces stillclaimed it was not:
scenarios/live-core-enforcement/docker-compose.yml'sheader comment + the
aa-gatewayservice's inline "not published yet" note,and
.github/workflows/verify-live.yml's header note about why thelive-core-enforcement-livejob (inverify-scenarios.yml) staysworkflow_dispatch-only. Both are corrected to state the image is published,citing the same GHCR tags, while leaving the still-accurate
workflow_dispatch-only/quarantine rationale (redundant CI weight vs.verify-live.yml's dailyaasm start --mode locallane) intact. Comment-only— no job triggers or runtime behavior changed.
Companion cleanup to AAASM-4743 (README) and AAASM-4771
(
verify-scenarios.ymljob comment), which already corrected the same staleclaim elsewhere.
Related ticket
https://lightning-dust-mite.atlassian.net/browse/AAASM-4773
Closes AAASM-4773
Fixes AAASM-4773
How to verify
python3 -c "import yaml; yaml.safe_load(open('scenarios/live-core-enforcement/docker-compose.yml'))"— parses cleanly.python3 -c "import yaml; yaml.safe_load(open('.github/workflows/verify-live.yml'))"— parses cleanly.image:,on:,continue-on-error:, and job steps are untouched.Checklist
[AAASM-XXXX] <GitEmoji> (<scope>): <summary>.envfiles committedREADME.mdwith prerequisites and run instructions