fix(devcontainer): maintained .NET 10 base image and SDK 10.0.301 (runtime 10.0.9)#1015
Merged
Merged
Conversation
….301 (runtime 10.0.9) The devcontainer's base tag (devcontainers/dotnet:1-10.0-noble) was frozen upstream on an October 2025 RC-era image and never rebuilt after .NET 10 went GA, and the layered SDK pin (10.0.203, runtime 10.0.7) fell behind JIM.Web's RuntimeFrameworkVersion 10.0.9 when #983 introduced that pin, so native JIM.Web runs (jim-build-light, Generate-OpenApiDoc.ps1) failed at launch with "framework 10.0.9 not found" while Docker builds kept working. - Switch the base to the maintained 2.x image line, digest-pinned per the dependency pinning policy so Dependabot resumes proposing digest bumps (it cannot flag a dead tag: the digest never changes). - Bump the layered SDK pin to 10.0.301, which ships runtime 10.0.9, and document it as a sync point with RuntimeFrameworkVersion. - Drop the stale-Yarn-repo workaround (1.x-era; not present in the 2.x image) and update the PowerShell-removal rationale (the 2.x base ships stable pwsh, but setup.sh's pinned global tool remains canonical). - Add the devcontainer SDK pin to the RuntimeFrameworkVersion companion checklist in DEPENDENCY_PINNING.md and the review-dependabot skill so future .NET patch bumps carry it in the same commit. Verified: the devcontainer image builds clean on the new base, and native OpenAPI generation (the failing workflow) succeeds under a scratch install of SDK 10.0.301. A devcontainer rebuild is needed to pick this up. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
The devcontainer's base tag (
devcontainers/dotnet:1-10.0-noble) was frozen upstream on an October 2025 RC-era image (never rebuilt after .NET 10 GA), and the layered SDK pin (10.0.203 / runtime 10.0.7) fell behind JIM.Web'sRuntimeFrameworkVersion10.0.9 from #983, so native JIM.Web runs (jim-build-light,Generate-OpenApiDoc.ps1) failed at launch while Docker builds kept working.engineering/DEPENDENCY_PINNING.md, so Dependabot resumes digest bumps (it cannot flag a dead tag).RuntimeFrameworkVersion; the review-dependabot skill's companion-commit checklist now includes it, so future .NET patch bumps carry the devcontainer with them.Verified: devcontainer image builds clean on the new base; native OpenAPI generation succeeds under a scratch SDK 10.0.301 install (814 KB document, exit 0). Contributors need a devcontainer rebuild after this merges.
Docs: n/a - development tooling only; no user-facing change.
🤖 Generated with Claude Code