Skip to content

Releases: cloudposse/docs

v1.32.0

06 Jun 13:11
5261a56

Choose a tag to compare

Update posthog config @osterman (#761)

what

  • Use separate key

why

  • All data was flowing to our marketing site

v1.31.0

04 Jun 22:18
a309cb0

Choose a tag to compare

Correct Workshop Time 2 @milldr (#759)

what

  • corrected office hour time for quickstart

why

Starting next week, our Wednesday Customer Workshop will shift to 5:30 PM EDT / 4:30 PM CDT / 2:30 PM PDT (Thursday 7:30 AM in Sydney/Melbourne, 9:30 AM in New Zealand).

This adjustment is designed to better support teams in regions like Australia and New Zealand, while continuing to be accessible to our U.S. customer base (5:30 PM EDT / 4:30 PM CDT / 2:30 PM PDT, same day).

references

docs: remove release engineering strategy from quickstart kickoff @Benbentwo (#758)

Remove the 'Decide on Release Engineering Strategy' item from the quickstart and jumpstart kickoff design decisions lists and move the documentation to a deprecated folder.

Changes:

  • Remove the release engineering strategy item from both quickstart and jumpstart kickoff documentation
  • Move the release engineering strategy documentation to a deprecated folder
  • Update references to point to the deprecated location
  • Remove all references from handoff calls lists
  • Add redirect from old location to software delivery layer page

This change simplifies the quickstart and jumpstart processes by removing a non-essential design decision while maintaining the documentation for historical reference.

v1.30.0

01 Jun 18:37
3a125b0

Choose a tag to compare

Announce platform advisory @osterman (#757)

What

  • Adds new Platform Advisory support tier
  • Adds documentation page and blog post announcing the service
  • Clarifies positioning for Platform Advisory vs Essential Support and Flexible Support
  • Highlights fit for teams in fintech, health tech, and regulated industries where delays, mistakes, or failed migrations would cost big

Why

  • Provides a clear path for customers to de-risk migrations and get priority access to senior Cloud Posse engineers for high-stakes projects
  • Aligns documentation with current commercial open source positioning
  • Helps buyers understand when Platform Advisory is the right fit

v1.29.0

30 May 19:45
095fb65

Choose a tag to compare

Workshop #2 time @milldr (#755)

what

Changed time for workshop 2

why

Starting next week, our Wednesday Customer Workshop will shift to 5:30 PM EDT / 4:30 PM CDT / 2:30 PM PDT (Thursday 7:30 AM in Sydney/Melbourne, 9:30 AM in New Zealand).

This adjustment is designed to better support teams in regions like Australia and New Zealand, while continuing to be accessible to our U.S. customer base (5:30 PM EDT / 4:30 PM CDT / 2:30 PM PDT, same day).

references

  • DEV-3296
fixes markdown synthax for link @patlachance (#752)

what

fixed wrong synthax for markdown link

why

link not working

references

none, multiple other usage of markdown links in the document

Fix workflows for forks @goruha (#753)

what

  • Added repository: ${{ github.event.pull_request.head.repo.full_name }} for checkout action

why

  • Handle pull_request_target with forks
♻️ Localstack Demo Example @cloudpossebot (#748)

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#750

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#750

v1.28.0

09 May 13:48
05af12d

Choose a tag to compare

chore: Improve SuperAdmin docs @milldr (#747)

what

  • improved SuperAdmin docs

why

  • This page was missing our standard conventions for documentation

references

  • DEV-3154
chore: Deprecated `#refarch` References @milldr (#749)

what

  • removed all occurrences of #refarch

why

  • We have archived that channel and now require all support questions in GitHub Discussions

references

v1.27.0

24 Apr 17:40
f62c0c7

Choose a tag to compare

Improve Deployment Ordering Documentation @milldr (#746)

what

  • Move ECR to after GitHub
  • Add planners and necessary steps to reapply aws-teams

why

  • Improve the documentation ordering for deploying github oidc related components

references

♻️ Improve Deployment Ordering @milldr (#745)

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#749

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#749

v1.26.0

18 Apr 16:14
42bb3b2

Choose a tag to compare

Update docs for Geodesic v4 @Nuru (#722)

what

  • Update Geodesic documentation for version 4

why

  • Existing documentation is out of date and does not reflect current best practices

references

DEV-2495: Update FAQ for GitOps Labels @milldr (#744)

what

  • Add a FAQ for all GitOps labels

why

  • the previous list was incomplete

references

  • DEV-2495
DEV-2502: Reference Page Introduction @milldr (#743)

what

  • Add introductory content to the reference section

why

  • Replace the placeholder. Explain this page

references

  • DEV-2502
DEV-2490: Formatting for Compliance Setup @milldr (#742)

what

  • Fix the formatting for compliance and security set up

why

  • Steps were not formatting correctly

references

  • DEV-2490

v1.25.0

14 Apr 16:34
e4fa71f

Choose a tag to compare

chore: Community Testing Documentation Improvements @milldr (#741)

what

  • Clean up the documentation pages for testing

why

  • Update conventions, formatting, spelling
  • Add FAQs I've encountered

references

  • n/a
feat: Poly Repo Strategy @milldr (#740)

what

  • Document poly repo strategy with account-map

why

  • This has come up a few times recently

references

Argo CD GitHub App Usage @milldr (#739)

what

  • Document using GitHub Apps for Argo CD rather than GitHub PATs

why

  • GitHub Apps are now supported for Argo CD as the preferred auth method.

references

  • .
DEV-123: Update Release Engineering docs to include snippet on consolidating workflows @Benbentwo (#708)

what

  • Update Release Engineering docs to include snippet on consolidating workflows

why

  • Docs
  • More upfront docs during handoff

v1.24.0

27 Mar 22:18
bc58dbf

Choose a tag to compare

Fix component testing cheatsheet @goruha (#738)

what

  • Fix component testing cheatsheet

why

  • Current cheatsheet have wrong info

v1.23.0

26 Mar 15:52
4a9f9ec

Choose a tag to compare

feat: Announcements @milldr (#737)

what

  • Create support for Announcements

why

  • We need somewhere to put announcements that we can link and refer to

references