Skip to content

test: move the test apps, native e2e suites and upgrade-in-place onto Auth (stack 11/14) - #860

Open
harsh62 wants to merge 1 commit into
auth/stack-10-bb-auth-ui-and-migrationfrom
auth/stack-11-consumers-on-auth
Open

harsh62 wants to merge 1 commit into
auth/stack-10-bb-auth-ui-and-migrationfrom
auth/stack-11-consumers-on-auth

Conversation

@harsh62

@harsh62 harsh62 commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Part 11 of 14 of the auth-unification stack · stacked on auth/stack-10-bb-auth-ui-and-migration (part 10) · reference PR #711 has the whole change in one commit.
Merge bottom to top. When the PR below merges, GitHub retargets this one to main.

Problem

Moves every private consumer onto Auth before anything is deleted.

Issue #, if available: see #711

Changes

  • The comprehensive test app: every auth instance is now Auth, including the Secret block's gated test methods.
  • The hosting apps:
    • Next.js, SPA and Nuxt are on Auth, with the deploy done in Playwright globalSetup;
    • Astro and SvelteKit get the same lifecycle changes.
  • Other test apps: native-bindings, amplify-gen2 on Auth.fromExisting (no hand-written verifier), vpc-smoke, auth-cognito-passkeys.
  • Native: the e2e suites and examples (Kotlin, Swift, Dart) on Auth.
  • The upgrade-in-place harness and workflow: AuthCognito 0.1.12 → Auth must reach UPDATE_COMPLETE with the same pool, users and sessions, and the old cookie must still work.
  • The live-spec check for fixtures 18 and 23.

What to review closely: These apps are private, so they can import @aws-blocks/bb-auth straight from the workspace. The deployed e2e builds gate their test-only methods (testSupport: account creation, the admin surface, secret values) behind a secret that is made fresh for each run and passed through BLOCKS_TEST_SUPPORT_SECRET, so neither CI nor the tests read it from AWS and the CI role needs no new permission (L35, R124). Check that a normal build still has no testSupport namespace (test-support-synth.test.ts).

Validation

This branch passed on its own:

  • npm ci, with the lockfile unchanged by npm install
  • lint and lint:deps
  • build
  • the exports, client user-agent and packed-asset checks
  • check:api
  • the action-pin guard and the catalog check
  • all four changeset-guard checks
  • test:unit: 7,754 passed, 1 failed (main's timing-sensitive framework-sink test, which counts shared temp folders; it passes on its own)
  • test:e2e:local (and vendorize): 502 passed, 0 failed
  • native goldens regenerate with zero drift
  • Swift: golden compile, swift build, codegen and runtime tests, SwiftFormat

The per-run test-support secret (R124) was proven on AWS too, on new stacks that were destroyed afterwards: comprehensive sandbox e2e 431/431 with the secret set the way CI sets it, and hosting-spa sandbox e2e 11 passed (1 skipped by design) with globalSetup generating it. CloudTrail for the run shows no ssm:GetParameter call by the test process, and none on a test-support parameter; the only reads were the stack's own Lambda reading its blocks' secrets.

The full stack passed end to end on AWS, on new stacks that were destroyed afterwards: upgrade-in-place from AuthCognito, comprehensive sandbox and production, hosting, native, and the CloudFront front door (see #711). That run was on the tree before the latest merges of main (#824's synth guards, #797's Swift Blocks entry point, #834's template metadata, #835/#837's native opt-out warnings, #841, #749, #819 and dependency bumps, then #208's submitAuthAction, #807's Swift typed declared-binding results, #637's config-bucket hardening and more dependency bumps); the merged tree, which part 12 is, passed every local gate, including the native suites and the Swift e2e against a local backend.

Checklist

  • PR description included
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@harsh62
harsh62 added this pull request to stack #864 October 19, 2026 00:58
@changeset-bot

changeset-bot Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 926b2f4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

This branch was successfully deployed

1 active (outdated) and 1 inactive deployments
agent-bench — 926b2f4a Deployed Oct 22, 2026 by harsh62 via bench / summary #3273
publish — 9b7b0a54 Deployed Oct 20, 2026 by harsh62 via bench / summary #3077
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant