From 1e755f33bde7ebb8ee378d1d37378a1709bddd80 Mon Sep 17 00:00:00 2001 From: Cristian Greco Date: Wed, 8 Apr 2026 09:37:56 +0100 Subject: [PATCH 1/5] Document LocalStack authentication requirements --- docs/modules/localstack.md | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/docs/modules/localstack.md b/docs/modules/localstack.md index 634f24960..5a2fc201c 100644 --- a/docs/modules/localstack.md +++ b/docs/modules/localstack.md @@ -16,9 +16,29 @@ These examples use the following libraries: Choose an image from the [container registry](https://hub.docker.com/r/localstack/localstack) and substitute `IMAGE`. +!!! note "Authentication requirements" + Starting on March 23, 2026, LocalStack moved to authenticated image releases. Older pinned tags may continue to work without `LOCALSTACK_AUTH_TOKEN`, but newer releases require it. + + Prefer pinning a specific image tag instead of using `latest`. If the image tag you use requires authentication, pass `LOCALSTACK_AUTH_TOKEN` when starting the container: + + ```typescript + const token = process.env.LOCALSTACK_AUTH_TOKEN; + + if (!token) { + throw new Error("LOCALSTACK_AUTH_TOKEN must be set for authenticated LocalStack images"); + } + + const container = await new LocalstackContainer("localstack/localstack:IMAGE") + .withEnvironment({ LOCALSTACK_AUTH_TOKEN: token }) + .start(); + ``` + + Refer to the [LocalStack announcement](https://blog.localstack.cloud/localstack-single-image-next-steps/) for the current rollout details. + ### Create a S3 bucket + [](../../packages/modules/localstack/src/localstack-container.test.ts) inside_block:localstackCreateS3Bucket + - \ No newline at end of file From 78ac3da7ab520b0eab48c291a2461cd76f8be45a Mon Sep 17 00:00:00 2001 From: Cristian Greco Date: Wed, 8 Apr 2026 09:41:58 +0100 Subject: [PATCH 2/5] Fix LocalStack docs code include spacing --- AGENTS.md | 1 + docs/modules/localstack.md | 2 -- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index edcf633d9..48dd71371 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -20,6 +20,7 @@ It captures practical rules that prevent avoidable CI and PR churn. - If a public API changes, update the relevant docs in the same PR. - If new types are made part of the public API, export them from the package's `index.ts` in the same PR. - If new learnings or misunderstandings are discovered, propose an `AGENTS.md` update in the same PR. +- In docs Markdown, keep `` blocks tight with no blank lines between the markers and the include line, or the rendered snippet will contain blank lines between code lines. - Tests should verify observable behavior changes, not only internal/config state. - Example: for a security option, assert a real secure/insecure behavior difference. - Test-only helper files under `src` (for example `*-test-utils.ts`) must be explicitly excluded from package `tsconfig.build.json` so they are not emitted into `build` and accidentally published. diff --git a/docs/modules/localstack.md b/docs/modules/localstack.md index 5a2fc201c..952eac576 100644 --- a/docs/modules/localstack.md +++ b/docs/modules/localstack.md @@ -38,7 +38,5 @@ Choose an image from the [container registry](https://hub.docker.com/r/localstac ### Create a S3 bucket - [](../../packages/modules/localstack/src/localstack-container.test.ts) inside_block:localstackCreateS3Bucket - From bb624d40fa12b726a226ecfeab59d4d654fdafcc Mon Sep 17 00:00:00 2001 From: Cristian Greco Date: Wed, 8 Apr 2026 09:49:13 +0100 Subject: [PATCH 3/5] Clarify PR title naming guidance --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 48dd71371..883d24621 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -51,7 +51,7 @@ It captures practical rules that prevent avoidable CI and PR churn. - Never bypass signing (for example, do not use `--no-gpg-sign`). - If signing fails (for example, passphrase/key issues), stop and ask the user to resolve signing, then retry. 8. Push branch. Ask for explicit user permission before any force push. -9. Open PR against `main` using a human-readable title (no `feat(...)` / `fix(...)` prefixes). +9. Open PR against `main` using a human-readable title (no `feat(...)` / `fix(...)` prefixes, and no agent-identifying prefixes or suffixes). - When using `gh` to create/edit PR descriptions, prefer `--body-file ` over inline `--body`. - This avoids shell command substitution issues when the body contains backticks. 10. Add labels for both change type and semantic version impact. From 57f8655d51cbd30431dc27c8e5dd9b9c2009facd Mon Sep 17 00:00:00 2001 From: Cristian Greco Date: Wed, 8 Apr 2026 09:51:31 +0100 Subject: [PATCH 4/5] Default PRs to ready for review --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 883d24621..e86e8069f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -52,6 +52,7 @@ It captures practical rules that prevent avoidable CI and PR churn. - If signing fails (for example, passphrase/key issues), stop and ask the user to resolve signing, then retry. 8. Push branch. Ask for explicit user permission before any force push. 9. Open PR against `main` using a human-readable title (no `feat(...)` / `fix(...)` prefixes, and no agent-identifying prefixes or suffixes). + - Default to a ready-for-review PR. Only open or keep a PR in draft when the user explicitly asks for a draft. - When using `gh` to create/edit PR descriptions, prefer `--body-file ` over inline `--body`. - This avoids shell command substitution issues when the body contains backticks. 10. Add labels for both change type and semantic version impact. From 15e1bceae0dd8d5e3bf507d691d95a56a77ed36a Mon Sep 17 00:00:00 2001 From: Cristian Greco Date: Wed, 8 Apr 2026 09:53:36 +0100 Subject: [PATCH 5/5] Tighten PR body-file guidance --- AGENTS.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index e86e8069f..d2a52a78b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -53,8 +53,7 @@ It captures practical rules that prevent avoidable CI and PR churn. 8. Push branch. Ask for explicit user permission before any force push. 9. Open PR against `main` using a human-readable title (no `feat(...)` / `fix(...)` prefixes, and no agent-identifying prefixes or suffixes). - Default to a ready-for-review PR. Only open or keep a PR in draft when the user explicitly asks for a draft. - - When using `gh` to create/edit PR descriptions, prefer `--body-file ` over inline `--body`. - - This avoids shell command substitution issues when the body contains backticks. + - When using `gh` to create/edit PR descriptions, prefer `--body-file ` over inline `--body`; this avoids shell command substitution issues when the body contains backticks. 10. Add labels for both change type and semantic version impact. 11. Ensure PR body includes: - summary of changes