Add .devcontainer/devcontainer.json reference config#18379
Open
JoshFerge wants to merge 1 commit into
Open
Conversation
Adds a Dev Container config for sentry-docs that doubles as the source-of-truth environment config for Sentry's coding-agent sandbox (Per-Repo Environments, AIML-2937). The sandbox honors the lifecycle commands (corepack enable + pnpm install --frozen-lockfile) and containerEnv, while ignoring image/build/features for security. The image + node version apply to local Dev Containers / Codespaces. Verified in the universal sandbox image: - pnpm install --frozen-lockfile resolves the lockfile and installs cleanly (pnpm auto-pinned to 10.30.0 via packageManager). - pnpm build runs end to end (enforce-redirects, generate-og-images, generate-doctree, next build) once NEXT_PUBLIC_SENTRY_DSN is set — hence the containerEnv entry. Static generation covers ~10k pages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Adds a Dev Container config for sentry-docs. Standard
devcontainer.json(VS Code Dev Containers / GitHub Codespaces) that also serves as the source-of-truth environment config for Sentry's coding-agent sandbox (Per-Repo Environments, part of AIML-2937).What the coding-agent sandbox honors vs ignores
onCreateCommand/updateContentCommand/postCreateCommand,containerEnv,remoteEnvimage,build/dockerfile,featuresThe sandbox runs on its own hardened, multi-language base image; the
image+ node version here only apply to local Dev Containers / Codespaces. The repo pins node 22.16.0 / pnpm 10.30.0 viapackage.json(volta+packageManager).Lifecycle
onCreateCommand/updateContentCommand:corepack enable && pnpm install --frozen-lockfilecontainerEnv:NODE_OPTIONS(build headroom) +NEXT_PUBLIC_SENTRY_DSN(a public client key;next.config.tsrequires it for a production build — placeholder for dev/CI, override for prod deploy)Verified in the universal sandbox image
pnpm install --frozen-lockfileresolves the lockfile and installs cleanly; pnpm auto-pinned to 10.30.0 viapackageManager.pnpm buildruns end to end —enforce-redirects,generate-og-images(2541 files scanned),generate-doctree, thennext buildstatic generation across ~10k pages — onceNEXT_PUBLIC_SENTRY_DSNis set.🤖 Generated with Claude Code
Agent transcript: https://claudescope.sentry.dev/share/tehgJLfYHA86brLj-Cn-6jy-b5NcSf3HK_3KeckRulA