You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Next.js uses findUp which crawls and looks for a next.config.ts. The problem was that @workflow/web was missing a next.config.ts when built and so when running it inside a Next.js project, would resolve to the current Next.js project's next.config.ts.
…eview
Point the world-vercel HTTP client at the workflow-server#646 preview
deployment (head a588ed3d) so this PR's e2e/integration lanes exercise
the real batched POST /api/v4/runs/:runId/events/batch backend before
#646 is promoted to production.
Probed pre-pin: POST /api/v4/runs/<fake>/events/batch returns 401 (auth),
not a route-404 — the batch route is served by the preview.
This is an intentional review-time pin. The CI lint rule requiring
WORKFLOW_SERVER_URL_OVERRIDE to be empty on `main` will fail while this
is present; that failure is the deliberate merge gate, not something to
work around. Removal is a single-line revert to '' once #646 deploys to
production.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…alias
Point WORKFLOW_SERVER_URL_OVERRIDE at the branch-tracking alias
https://workflow-server-git-pgp-batch-step-transitions.vercel.sh instead of
the stale v1 deployment URL (8sp9l2esp predates the fence + full grammar).
The alias always resolves to the latest deployment of the server branch, so
future #646 pushes need no re-pin here. Authenticated probe: the batch route
returns 302 -> Vercel SSO (protected, route exists), not a 404.
Floats-with-branch caveat is documented (a server force-push mid-CI could
shift the backend under a running e2e round — acceptable for review). The
"No Test Overrides" lint intentionally FAILS while this pin is present — the
deliberate merge gate.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Next.js uses
findUpwhich crawls and looks for anext.config.ts. The problem was that@workflow/webwas missing anext.config.tswhen built and so when running it inside a Next.js project, would resolve to the current Next.js project'snext.config.ts.fixes#115 and #381