test(e2e): pin provider v0.13.0 and verifier v0.10.0 release cuts before tagging - #34
Conversation
auth.provider added `@o3co/auth-provider-federation-oidc` this cycle, and its standalone template depends on it. The e2e provider Dockerfile lists each package by hand in three places (deps install, runtime package.json, dist), and did not follow, so the image failed at `pnpm install` with ERR_PNPM_WORKSPACE_PKG_NOT_FOUND — the same miss #432's device-grant had. With the three lines added, `make test-e2e` passes against auth.provider develop a82a76be and auth.policy-verifier develop 3291ea98 (token-flow 20/20, abac 19/19). The pins themselves move in the release cut. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
🟢 Approval recommended
The required package is included across all provider image build stages.
Pull request overview
Updates the provider E2E Docker image to include the federation OIDC package.
Changes:
- Adds package metadata to dependency and runtime stages.
- Copies the built distribution into the runtime image.
File summaries
| File | Description |
|---|---|
tests/dockerfiles/provider.Dockerfile |
Includes federation OIDC in all required image stages. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Why Plan: this PR lands with the release pin bump. The |
…ore tagging Pre-tag E2E for both minor releases, in the order the release rule requires: cut merged -> umbrella E2E green -> tag. PROVIDER_REV moves from 84609f33 (v0.12.1) to 4c44adfbf8e780863c1d7c22bf0129a86bdc62d9 (release: v0.13.0, o3co/auth.provider#585). VERIFIER_REV moves from 6d6a26a4 (v0.9.0) to cc982b795efc8807712b3db9ef596182a3bfd815 (release: v0.10.0, o3co/auth.policy-verifier#240). PROXY_REV / PROVIN_REV are unchanged. The provider pin needs the previous commit: its standalone template depends on the new @o3co/auth-provider-federation-oidc, which the provider image did not carry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
y1o1
changed the title
Summary
Pre-tag E2E for both minor releases, in the order the release rule requires: cut merged → umbrella E2E green → tag.
PROVIDER_REV: 84609f33 (v0.12.1) →4c44adfb(release: v0.13.0, release: v0.13.0 auth.provider#585)VERIFIER_REV: 6d6a26a4 (v0.9.0) →cc982b79(release: v0.10.0, release: v0.10.0 auth.policy-verifier#240)PROXY_REV/PROVIN_REVunchangedThe provider image carries federation-oidc. auth.provider v0.13.0 adds
@o3co/auth-provider-federation-oidc, and its standalone template depends on it.tests/dockerfiles/provider.Dockerfilelists packages by hand in three places (deps install, runtimepackage.json,dist) and did not include it, so the provider image failed to build:Three lines added, one per list. The policy-verifier Dockerfile needs nothing: its template depends only on core, builtins and server. The Dockerfile change alone fails CI against the old provider pin (the package does not exist there), so the two land together.
Test plan
make test-e2e PROVIDER_REV=a82a76be… VERIFIER_REV=3291ea98…locally (develop of both before the cut) — token-flow 20/20, abac 19/19test-e2eandprovin-compatibilitygreen at the pinned release-cut merge commitsAfter merge: tag
v0.10.0on cc982b79 andv0.13.0on 4c44adfb. #33 (amr/acr claims-contract row) merges with or after this.🤖 Generated with Claude Code