fix: Associate devcontainer blog posts with v1.201.0 release

[osterman]

what

• Add release: v1.201.0 to the frontmatter of the devcontainer blog posts

why

These blog posts were released in v1.201.0, but subsequent corrections to them (fixing dates/tags in #1856) are currently unreleased. Without the release: field, these corrections cause the posts to appear in the "Unreleased" section of the changelog. By explicitly setting release: v1.201.0, we retroactively associate them with their original release, so the corrections don't show up as unreleased changes.

references

• Devcontainer feature was released in v1.201.0
• Date/tag corrections made in fix: Remove invalid blog tags and fix devcontainer post dates #1856

Summary by CodeRabbit

• Documentation
  • Updated metadata on blog posts related to development container support.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Two blog post files received a release metadata field (v1.201.0) added to their front matter. No content modifications.

Changes

Cohort / File(s)	Summary
Blog metadata augmentation website/blog/2025-12-05-geodesic-production-ready-devcontainer.mdx, website/blog/2025-12-05-native-devcontainer-support.mdx	Added release: v1.201.0 to front matter metadata

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

no-release

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding release metadata to devcontainer blog posts.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch osterman/blog-post-dates-fix

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 15bfcdf and b2b6fb0.

📒 Files selected for processing (2)

• website/blog/2025-12-05-geodesic-production-ready-devcontainer.mdx (1 hunks)
• website/blog/2025-12-05-native-devcontainer-support.mdx (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

website/**

📄 CodeRabbit inference engine (.cursor/rules/atmos-rules.mdc)

website/**: Update website documentation in the website/ directory when adding new features, ensure consistency between CLI help text and website documentation, and follow the website's documentation structure and style
Keep website code in the website/ directory, follow the existing website architecture and style, and test website changes locally before committing
Keep CLI documentation and website documentation in sync and document new features on the website with examples and use cases

Files:

• website/blog/2025-12-05-geodesic-production-ready-devcontainer.mdx
• website/blog/2025-12-05-native-devcontainer-support.mdx

website/**/*.mdx

📄 CodeRabbit inference engine (CLAUDE.md)

ALWAYS build website after doc changes: cd website && npm run build. Verify: no broken links, missing images, MDX component rendering.

Files:

• website/blog/2025-12-05-geodesic-production-ready-devcontainer.mdx
• website/blog/2025-12-05-native-devcontainer-support.mdx

website/blog/**/*.mdx

📄 CodeRabbit inference engine (CLAUDE.md)

website/blog/**/*.mdx: Follow PR template (what/why/references). PRs labeled minor/major MUST include blog post: website/blog/YYYY-MM-DD-feature-name.mdx. Use .mdx with YAML front matter, <!--truncate--> after intro. MUST use tags from website/blog/tags.yml only. MUST use existing author from website/blog/authors.yml or add new entry.
Blog posts must have YAML frontmatter with: slug, title, authors, tags. Use <!--truncate--> after introduction. Valid tags must be from website/blog/tags.yml.

Files:

• website/blog/2025-12-05-geodesic-production-ready-devcontainer.mdx
• website/blog/2025-12-05-native-devcontainer-support.mdx

🧠 Learnings (12)

📓 Common learnings

Learnt from: CR
Repo: cloudposse/atmos PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-10T23:12:15.768Z
Learning: Applies to website/blog/**/*.mdx : Follow PR template (what/why/references). PRs labeled `minor`/`major` MUST include blog post: `website/blog/YYYY-MM-DD-feature-name.mdx`. Use `.mdx` with YAML front matter, `<!--truncate-->` after intro. MUST use tags from `website/blog/tags.yml` only. MUST use existing author from `website/blog/authors.yml` or add new entry.

Learnt from: Listener430
Repo: cloudposse/atmos PR: 934
File: tests/fixtures/scenarios/docs-generate/README.md.gotmpl:99-118
Timestamp: 2025-01-25T03:51:57.689Z
Learning: For the cloudposse/atmos repository, changes to template contents should be handled in dedicated PRs and are typically considered out of scope for PRs focused on other objectives.

📚 Learning: 2024-11-12T03:15:15.627Z

Learnt from: aknysh
Repo: cloudposse/atmos PR: 775
File: examples/quick-start-advanced/Dockerfile:9-9
Timestamp: 2024-11-12T03:15:15.627Z
Learning: It is acceptable to set `ARG ATMOS_VERSION` to a future version like `1.105.0` in `examples/quick-start-advanced/Dockerfile` if that will be the next release.

Applied to files:

• website/blog/2025-12-05-geodesic-production-ready-devcontainer.mdx
• website/blog/2025-12-05-native-devcontainer-support.mdx

📚 Learning: 2025-12-10T23:12:15.768Z

Learnt from: CR
Repo: cloudposse/atmos PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-10T23:12:15.768Z
Learning: Use Atmos agents for specialized domains: agent-developer for agent creation, tui-expert for Terminal UI, atmos-errors for error handling, flag-handler for CLI commands.

Applied to files:

• website/blog/2025-12-05-geodesic-production-ready-devcontainer.mdx
• website/blog/2025-12-05-native-devcontainer-support.mdx

📚 Learning: 2025-12-10T23:12:15.768Z

Learnt from: CR
Repo: cloudposse/atmos PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-10T23:12:15.768Z
Learning: Applies to website/blog/**/*.mdx : Follow PR template (what/why/references). PRs labeled `minor`/`major` MUST include blog post: `website/blog/YYYY-MM-DD-feature-name.mdx`. Use `.mdx` with YAML front matter, `<!--truncate-->` after intro. MUST use tags from `website/blog/tags.yml` only. MUST use existing author from `website/blog/authors.yml` or add new entry.

Applied to files:

• website/blog/2025-12-05-native-devcontainer-support.mdx

📚 Learning: 2025-03-18T12:26:25.329Z

Learnt from: Listener430
Repo: cloudposse/atmos PR: 1149
File: tests/snapshots/TestCLICommands_atmos_vendor_pull_ssh.stderr.golden:7-7
Timestamp: 2025-03-18T12:26:25.329Z
Learning: In the Atmos project, typos or inconsistencies in test snapshot files (such as "terrafrom" instead of "terraform") may be intentional as they capture the exact output of commands and should not be flagged as issues requiring correction.

Applied to files:

• website/blog/2025-12-05-native-devcontainer-support.mdx

📚 Learning: 2025-09-05T14:57:37.360Z

Learnt from: RoseSecurity
Repo: cloudposse/atmos PR: 1448
File: cmd/ansible.go:26-28
Timestamp: 2025-09-05T14:57:37.360Z
Learning: The Atmos codebase uses a consistent pattern for commands that delegate to external tools: `PersistentFlags().Bool("", false, doubleDashHint)` where doubleDashHint provides help text about using double dashes to separate Atmos options from native command arguments. This pattern is used across terraform, packer, helmfile, atlantis, aws, and ansible commands.

Applied to files:

• website/blog/2025-12-05-native-devcontainer-support.mdx

📚 Learning: 2025-09-13T16:39:20.007Z

Learnt from: samtholiya
Repo: cloudposse/atmos PR: 1466
File: cmd/markdown/atmos_toolchain_aliases.md:2-4
Timestamp: 2025-09-13T16:39:20.007Z
Learning: In the cloudposse/atmos repository, CLI documentation files in cmd/markdown/ follow a specific format that uses " $ atmos command" (with leading space and dollar sign prompt) in code blocks. This is the established project convention and should not be changed to comply with standard markdownlint rules MD040 and MD014.

Applied to files:

• website/blog/2025-12-05-native-devcontainer-support.mdx

📚 Learning: 2025-01-17T00:18:57.769Z

Learnt from: aknysh
Repo: cloudposse/atmos PR: 944
File: go.mod:206-206
Timestamp: 2025-01-17T00:18:57.769Z
Learning: For indirect dependencies with license compliance issues in the cloudposse/atmos repository, the team prefers to handle them in follow-up PRs rather than blocking the current changes, as these issues often require deeper investigation of the dependency tree.

Applied to files:

• website/blog/2025-12-05-native-devcontainer-support.mdx

📚 Learning: 2025-11-07T14:52:55.217Z

Learnt from: osterman
Repo: cloudposse/atmos PR: 1761
File: docs/prd/claude-agent-architecture.md:331-439
Timestamp: 2025-11-07T14:52:55.217Z
Learning: In the cloudposse/atmos repository, Claude agents are used as interactive tools, not in automated/headless CI/CD contexts. Agent documentation and patterns should assume synchronous human interaction.

Applied to files:

• website/blog/2025-12-05-native-devcontainer-support.mdx

📚 Learning: 2025-11-09T19:06:58.470Z

Learnt from: osterman
Repo: cloudposse/atmos PR: 1752
File: pkg/profile/list/formatter_table.go:27-29
Timestamp: 2025-11-09T19:06:58.470Z
Learning: In the cloudposse/atmos repository, performance tracking with `defer perf.Track()` is enforced on all functions via linting, including high-frequency utility functions, formatters, and renderers. This is a repository-wide policy to maintain consistency and avoid making case-by-case judgment calls about which functions should have profiling.

Applied to files:

• website/blog/2025-12-05-native-devcontainer-support.mdx

📚 Learning: 2025-07-05T20:59:02.914Z

Learnt from: aknysh
Repo: cloudposse/atmos PR: 1363
File: internal/exec/template_utils.go:18-18
Timestamp: 2025-07-05T20:59:02.914Z
Learning: In the Atmos project, gomplate v4 is imported with a blank import (`_ "github.com/hairyhenderson/gomplate/v4"`) alongside v3 imports to resolve AWS SDK version conflicts. V3 uses older AWS SDK versions that conflict with newer AWS modules used by Atmos. A full migration to v4 requires extensive refactoring due to API changes and should be handled in a separate PR.

Applied to files:

• website/blog/2025-12-05-native-devcontainer-support.mdx

📚 Learning: 2024-12-03T05:18:49.169Z

Learnt from: aknysh
Repo: cloudposse/atmos PR: 810
File: internal/exec/terraform_utils.go:40-213
Timestamp: 2024-12-03T05:18:49.169Z
Learning: In the context of the Atmos project, it's acceptable for functions like `execTerraformOutput` to remain as single functions if they perform a single purpose, such as retrieving Terraform outputs for a component in a stack, even if the function is lengthy.

Applied to files:

• website/blog/2025-12-05-native-devcontainer-support.mdx

⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Acceptance Tests (windows)
• GitHub Check: Summary

🔇 Additional comments (2)

website/blog/2025-12-05-geodesic-production-ready-devcontainer.mdx (1)

1-8: Consistent with companion blog post; same verification applies.

This post mirrors the changes made to 2025-12-05-native-devcontainer-support.mdx, adding the same release: v1.201.0 metadata. Both posts will now be grouped together under the v1.201.0 release in the changelog. The metadata validity and build checks from the previous file apply here as well.

website/blog/2025-12-05-native-devcontainer-support.mdx (1)

1-8: Blog frontmatter is valid and complete.

Author osterman exists in authors.yml, tag feature is valid in tags.yml, and the release: v1.201.0 field follows the established pattern. The post includes the required <!--truncate--> marker and has proper YAML frontmatter with all necessary fields. Ready to merge.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

None

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.26%. Comparing base (15bfcdf) to head (b2b6fb0).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1863      +/-   ##
==========================================
- Coverage   73.26%   73.26%   -0.01%     
==========================================
  Files         551      551              
  Lines       53458    53458              
==========================================
- Hits        39165    39164       -1     
- Misses      11447    11449       +2     
+ Partials     2846     2845       -1     

Flag	Coverage Δ
unittests	73.26% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 5 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

These changes were released in v1.202.0-rc.1.

[github-actions]

These changes were released in v1.203.0-test.1.