chore(release): prepare 0.9.5#248
Merged
Merged
Conversation
- Set version to 0.9.5 in mix/shared.exs (drop the rc suffix) - Remove the 🔜 marker from the 0.9.5 row in the README version table (OTP columns already match devops/releases pins) - Bump the default installer YAMLs (aws/gcp) and the YAML guide example to 0.9.5 - Set the changelog release date: 0.9.5 (2026-07-08) - Regenerate published docs via mix docs - Document the release preparation checklist in AGENTS.md Risk assessment: - Impact: version metadata and docs only, no code changes. Tagging 0.9.5 from main after merge triggers the release build. - Blast radius: version pins, README table, installer defaults, changelog heading, generated docs tarball, AGENTS.md. - Regression risk: low. The release itself is exercised by the tag-triggered workflows (now matrix-based, see #246), recommend a quick rc test tag if extra caution is wanted. - Rollback: revert this commit before tagging.
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.
What changed and why
Release preparation for 0.9.5, following the checklist now documented in
AGENTS.md("Release Preparation"):mix/shared.exs:0.9.5-rc1->0.9.5README.md: removed the:soon:marker from the 0.9.5 row; verified the OTP columns (27.3.4.14 / 28.5.0.3) matchdevops/releases/otp-*/.tool-versionsdevops/installer/deployex-aws.yaml/deployex-gcp.yaml:version: "0.9.5"guides/docs/yaml/README.md: YAML example bumped to0.9.5(step found in the 0.9.4 release commit, now added to the documented checklist)CHANGELOG.md: heading set to## 0.9.5 🚀 (2026-07-08)mix docsrun to regenerateapps/deployex_web/priv/static/docs/docs.tar.gzAlso adds the "Release Preparation" section to
AGENTS.mdso the full checklist is documented for future releases.After merge: push the
0.9.5tag from main to triggerreleases.yaml. Note this will be the first release using the matrix-based workflows from #246 - consider a quick-rctest tag first if you want to exercise them beforehand.Risk assessment
🤖 Generated with Claude Code