Skip to content

docs: remind release engineers to update shared docs after each release - #1123

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

Closes #1116

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/typescript/ 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.

Docs-only change; no code or CI changes. Sibling PRs: aws-durable-execution-sdk-python #878, aws-durable-execution-sdk-java #843.

@hln33
hln33 marked this pull request as ready for review October 29, 2026 23:19
@hln33
hln33 deployed to ai-pr-review-runtime October 29, 2026 23:19 — with GitHub Actions Active
@hln33
hln33 deployed to ai-pr-review-runtime October 29, 2026 23:20 — with GitHub Actions Active
Comment thread RELEASING.md Outdated
Comment on lines +147 to +150
mdformat --check docs/
codespell docs/
python3 scripts/check_example_refs.py
zensical build --clean

This comment was marked as outdated.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/ai verdict accepted

Can probably remove this part. Anyone making changes to the docs repo should be running these checks already. If they do not run them, then the docs repo CI should run it and flag formatting violations.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recorded accepted for AI finding arf_v1_oaz244gk7us4cen5orsqixp6af.

@github-actions

This comment has been minimized.

@hln33
hln33 deployed to ai-pr-review-runtime October 31, 2026 00:01 — 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 d781ef8 to e00bbd6 Compare October 31, 2026 00:24
@hln33
hln33 deployed to ai-pr-review-runtime October 31, 2026 00:24 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown

Codex AI review

No actionable findings in the documentation-only diff. The prior external-validation concern is resolved. SDK invariants and contract tests are unchanged. Review was read-only; the external documentation workflow was not exercised.

Reviewed commit e00bbd6d3414323daecf71a705004f85fc60f872. Workflow run

This branch was successfully deployed

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