Skip to content

chore(release): prepare 0.9.5#248

Merged
thiagoesteves merged 1 commit into
mainfrom
thiagoesteves/prepare-release-0.9.5
Jul 8, 2026
Merged

chore(release): prepare 0.9.5#248
thiagoesteves merged 1 commit into
mainfrom
thiagoesteves/prepare-release-0.9.5

Conversation

@thiagoesteves

Copy link
Copy Markdown
Owner

What changed and why

Release preparation for 0.9.5, following the checklist now documented in AGENTS.md ("Release Preparation"):

  1. mix/shared.exs: 0.9.5-rc1 -> 0.9.5
  2. README.md: removed the :soon: marker from the 0.9.5 row; verified the OTP columns (27.3.4.14 / 28.5.0.3) match devops/releases/otp-*/.tool-versions
  3. devops/installer/deployex-aws.yaml / deployex-gcp.yaml: version: "0.9.5"
  4. guides/docs/yaml/README.md: YAML example bumped to 0.9.5 (step found in the 0.9.4 release commit, now added to the documented checklist)
  5. CHANGELOG.md: heading set to ## 0.9.5 🚀 (2026-07-08)
  6. mix docs run to regenerate apps/deployex_web/priv/static/docs/docs.tar.gz

Also adds the "Release Preparation" section to AGENTS.md so the full checklist is documented for future releases.

After merge: push the 0.9.5 tag from main to trigger releases.yaml. Note this will be the first release using the matrix-based workflows from #246 - consider a quick -rc test tag first if you want to exercise them beforehand.

Risk assessment

  • Impact: version metadata and docs only, no application code changes.
  • Blast radius: version pins, README table, installer defaults, changelog heading, generated docs tarball, AGENTS.md.
  • Regression risk: low for the PR itself; the release build runs on tag push.
  • Rollback: revert the commit before tagging.

🤖 Generated with Claude Code

- 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.
@thiagoesteves thiagoesteves self-assigned this Jul 8, 2026
@thiagoesteves thiagoesteves moved this to In Progress in DeployEx Project Jul 8, 2026
@thiagoesteves thiagoesteves merged commit f2b4911 into main Jul 8, 2026
3 checks passed
@thiagoesteves thiagoesteves deleted the thiagoesteves/prepare-release-0.9.5 branch July 8, 2026 12:44
@github-project-automation github-project-automation Bot moved this from In Progress to Done in DeployEx Project Jul 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant