Skip to content

Conversation

@osterman
Copy link
Member

Summary

  • Added comprehensive deprecation and archival process documentation to the community section
  • Created blog post announcing the new documentation
  • Documents the 7-step process for transparently deprecating and archiving repositories

Details

This PR adds structured documentation for how Cloud Posse handles component deprecation and archival. The process includes:

  1. Announce Deprecation via Pull Request - Communicate the plan with clear timelines
  2. Add Deprecation Notice to README - Using GitHub warning admonitions
  3. Update README.yaml - Add the deprecated field with notice text
  4. Create and Pin GitHub Issue - Comprehensive issue with migration guidance
  5. Link Issue in Deprecation Notice - Ensure visibility
  6. Wait for Deprecation Date - Typically 90+ days grace period
  7. Archive Repository - Update .github/settings.yml to set archived: true

The documentation is added to /community/contribute/our-github#deprecation-and-archival-process which seemed like the natural fit given the existing content about GitHub maintenance and archival.

A blog post has been added to announce this new documentation to the community.

Test Plan

  • Documentation renders correctly in MDX
  • All links are valid
  • Code examples are properly formatted
  • Blog post follows existing format

🤖 Generated with Claude Code

This commit adds comprehensive documentation for the process of deprecating
and archiving Cloud Posse components. The documentation includes a step-by-step
guide covering:

- Announcing deprecations via pull requests
- Adding warning admonitions to READMEs
- Updating README.yaml with deprecated field
- Creating and pinning GitHub issues
- Grace period for community migration
- Repository archival process

Also includes a blog post announcing the new documentation to the community.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
- Added explicit mention of cloudposse-terraform-components organization
- Clarified that the process applies to modules, components, and other tooling
- Updated both documentation and blog post for consistency

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@RoseSecurity
Copy link
Contributor

Should the GitHub Issue be created first? It’ll be referenced in the PR and any additional README updates made in the PR. I’m a bit confused about the ordering.

@osterman osterman merged commit fbf5555 into master Oct 16, 2025
2 checks passed
@osterman osterman deleted the osterman/deprecation-docs branch October 16, 2025 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants