Skip to content

docs: add shared-docs reminder to release guide - #881

Open
hln33 wants to merge 2 commits into
mainfrom
docs/releasing-shared-docs-step
Open

hln33 wants to merge 2 commits into
mainfrom
docs/releasing-shared-docs-step

Conversation

@hln33

@hln33 hln33 commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

Issue #, if available

Closes #878

Description of changes

Adds a ### 3. Update the shared documentation step to RELEASING.md under "Cutting a Release", and an "After publishing a release" checklist item. The step assigns the review of aws/aws-durable-execution-docs to the release engineer for every release, covers API references, guides, examples/python/ snippets, dependency versions, compatibility and migration text (not only version strings), gives a search command and the docs repo's checks, and asks the engineer to open or update the docs PR, link the release, and record "no changes needed" when applicable. Wording mirrors the existing section 4 of the Java SDK RELEASE.md. Sibling PRs: aws-durable-execution-sdk-js #1116, aws-durable-execution-sdk-java #843.

Design

See Rules for every change.

  • Design note (rule 3): not needed — documentation-only change to the human release process.
  • Simpler options considered (rule 2): a single checklist bullet. Rejected because the issue requires the reminder to cover changed behavior and examples, not only version strings.
  • Root cause (rule 5): not a bug fix.
  • Net change in source lines and in public API members: 0 source lines, 0 API members. RELEASING.md only.

Assumptions

  • The docs repository's checks are mdformat --check docs/, codespell docs/, python3 scripts/check_example_refs.py, zensical build --clean. Evidence: .github/workflows/quality.yml, scripts/check_example_refs.py and zensical.toml on aws-durable-execution-docs main, and the same list in the Java SDK RELEASE.md section 4.

Decisions not covered by the issue or the design note

  • The checklist addition is placed under a new "After publishing a release:" lead-in because the existing checklist is titled "Before publishing a release:" and the docs update happens after publication.

Checklist

  • Every new branch has a test that fails without it (rule 4) — N/A, documentation only
  • For a bug fix: the first commit adds a test that fails on the current code (rule 5) — N/A
  • Every edited test expectation is listed in the description, with the reason (rule 5) — N/A, no tests edited

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@hln33
hln33 marked this pull request as ready for review October 29, 2026 23:20
@hln33
hln33 deployed to ai-pr-review-runtime October 29, 2026 23:20 — with GitHub Actions Active
@hln33
hln33 deployed to ai-pr-review-runtime October 29, 2026 23:21 — with GitHub Actions Active
@github-actions

This comment has been minimized.

@hln33
hln33 deployed to ai-pr-review-runtime October 31, 2026 00:03 — with GitHub Actions Active
@github-actions

This comment has been minimized.

@hln33
hln33 force-pushed the docs/releasing-shared-docs-step branch from effb9d8 to 7db356c Compare October 31, 2026 00:20
@hln33 hln33 changed the title docs: remind release engineers to update shared docs after each release docs: add shared-docs reminder to release guide Oct 31, 2026
@hln33
hln33 deployed to ai-pr-review-runtime October 31, 2026 00:21 — with GitHub Actions Active
@github-actions

This comment has been minimized.

hln33 added 2 commits October 30, 2026 17:23
The mdformat, codespell, check_example_refs, and zensical commands
belong to aws/aws-durable-execution-docs. That repository documents
them in its CONTRIBUTING.md and runs them in CI. So the release guide
does not need to restate them.
@hln33
hln33 force-pushed the docs/releasing-shared-docs-step branch from 7db356c to 944668f Compare October 31, 2026 00:23
@hln33
hln33 deployed to ai-pr-review-runtime October 31, 2026 00:24 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown
Contributor

Codex AI review

No actionable findings after reviewing the complete diff against rules 1–9. This is a documentation-only change. No code was executed; external documentation links and command targets were not verified.

Reviewed commit 944668f1d2cb955997bf1886b6742c6e91f270c8. Workflow run

This branch was successfully deployed

1 active deployment
ai-pr-review-runtime — 944668f1 Deployed Oct 31, 2026 by hln33 via ai-pr-review / Codex review / Generate Codex review #2687
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.

[Docs]: Remind release engineers to update shared docs after each release

2 participants