What's Changed
[1.3.34] — 2026-05-11
Added
- ECR Docker Registry HTTP API V2 (
docker push/docker pull) — the registry V2 wire protocol now serves alongside the AWS API on the same gateway, matching real ECR. Covers/v2/ping,/v2/_catalog, chunked and single-shot blob upload, cross-repo blob mount, blob HEAD/GET/DELETE, manifest PUT/GET/HEAD/DELETE (by tag or digest), and/tags/list. Pushed images surface immediately inaws ecr describe-images; layer and manifest bytes persist underPERSIST_STATE=1. Routing fix bundled: registry paths previously fell through to S3 path-style and returned405; the new pre-empt matches only registry shapes (/blobs/,/manifests/,/tags/list) so API Gateway v2, AppSync Events, and SES v2 are unaffected. Reported by @LeTrungNguyen1703. - CloudFormation Custom Resource protocol —
Custom::*andAWS::CloudFormation::CustomResourcenow run the full Create / Update / Delete lifecycle. MiniStack mints a local/_ministack/cfn-response/{token}intercept in place of a pre-signed S3 ResponseURL, and the provisioner runs inasyncio.to_threadso the loop stays free for the Lambda's PUT callback — required for CDKcr.Provider-backed Lambdas.UpdateforwardsOldResourceProperties;Deletecarries thePhysicalResourceIdfromCreate;PhysicalResourceIdfalls back toRequestIdwhen the Lambda omits it.ServiceTokenaccepts bare function names or full Lambda ARNs. Contributed by @hiddengearz.
Fixed
- Cognito OAuth2
nonceechoed intoid_token— the authorize endpoint already stored the client-suppliednonceon the auth code, but/oauth2/tokennever threaded it into the minted id_token. Per OIDC Core 1.0 §3.1.3.7, strict OIDC libraries (oidc-client-ts,react-oidc-context, Auth0 / Microsoft clients) discard tokens missing an expected nonce. Now stamped on the id_token only; access and refresh tokens unchanged. Contributed by @coezbek.