test(e2e): pin the released component revisions (provider v0.12.0, verifier v0.8.0, proxy v0.5.0) - #27
Merged
Conversation
…rifier v0.8.0, proxy v0.5.0) The pins were the 2026-09-05 remediation HEADs. Since then provider v0.12.0, verifier v0.8.0 and proxy v0.5.0 were tagged and published, and each carries changes the umbrella has never exercised — the @o3co/auth.utils internalization in proxy and verifier, and the standalone-template shutdown fixes (bounded cleanup, deferred exit, reason consistency) in all three. This pins exactly the tagged trees, not develop: verifier and proxy develop are one commit past their tags, and the question this run answers is whether what shipped works together. Updating the baseline means updating these pins and rerunning the E2E, which the PR trigger does. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
There was a problem hiding this comment.
🟢 Approval recommended
The change is a straightforward, internally consistent pin update matching the PR description, with no additional logic modifications.
Pull request overview
Updates the pinned component git revisions used by this repo’s umbrella E2E workflow so the run exercises the exact provider/verifier/proxy trees that were tagged and released (rather than prior remediation HEADs), aligning the integration tests with what actually shipped.
Changes:
- Bump
PROVIDER_REVto19ce4c7f...(provider v0.12.0). - Bump
PROXY_REVto9828a137...(proxy v0.5.0). - Bump
VERIFIER_REVtoc5e0608c...(verifier v0.8.0).
File summaries
| File | Description |
|---|---|
| Makefile | Updates the pinned component revisions used by setup, build, and test-e2e to match the published release tags. |
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.
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.
Bumps the three component pins from the 2026-09-05 remediation HEADs to the trees that were actually tagged and published today:
8f97fa6619ce4c7f= v0.12.0a7465a2cc5e0608c= v0.8.07db91c2a9828a137= v0.5.0Why this run matters
Each release carries changes the umbrella has never exercised: the
@o3co/auth.utilsinternalization in proxy (#81) and verifier (#210) — new in-tree logger, shutdown, healthcheck, bearer parsing and request-id middleware — and the standalone-template shutdown fixes (bounded cleanup, deferred exit, reason consistency) in all three (#511, #83, #212).The release rule for this stack is umbrella E2E green, then tag. These tags went out before that run; this PR is the run, pinned to exactly what shipped. If it fails, the fix goes through
tests/here first, and a patch release follows.Pinned to the tags, not develop: verifier and proxy develop are each one commit past their tag (the reason-consistency follow-ups), and the question this answers is whether the published revisions work together.
UTILS_REVandPROVIN_REVare unchanged.🤖 Generated with Claude Code