Repository navigation
[AISAGE-502] ci: build the ai-gateway app on relevant changes - #7105
Merged
Merged
Conversation
Run next build for apps/ai-gateway with the same dummy environment the web build uses whenever the app, a workspace package, or the lockfile changes, so a broken gateway build fails before it reaches a deploy.
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge CI-only change: the Files Reviewed (2 files)
Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
4 of 5 tasks
iscekic
approved these changes
Oct 5, 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
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
Prep PR split out of #7052. Adds a
build-ai-gatewayCI job that runsnext buildforapps/ai-gateway, so a broken gateway build fails on the PR rather than at deploy time. The gateway is already onmain(#6806) but CI never builds it.buildjob. It also copiesapps/web/.envandapps/web/.env.testinto the app directory, because the gateway runs with the web app's environment (seeapps/ai-gateway/scripts/dev.sh).ai_gatewaypaths filter gates the job. It matchesapps/ai-gateway/**,packages/**, the web env files,ci.yml,package.jsonand the lockfile.packages/**is broad on purpose:web-sharedimports many workspace packages and their dependencies, and the build takes about a minute.scripts/changes-filter-retry.test.mjsnow expects the new filter name.mainstill notify Slack throughnotify-main-failure.yml, which watches the whole CI run.Verification
node --test scripts/changes-filter-retry.test.mjs scripts/stacked-ci.test.mjs scripts/deployment-workflows.test.mjspasses (39 tests).apps/ai-gateway, with the same env values and env-file copies the job uses: it builds in about 15s. The job has also passed on [AISAGE-502] feat(ai-gateway): add a manual Vercel deploy for kilocode-ai-gateway #7052.Visual Changes
N/A
Reviewer Notes
This PR changes
ci.yml, so thecloud-agent-nextsuite runs on it too. That suite flaked once on #7052 (a miniflare worker exited unexpectedly) and passed on rerun.