Skip to content

docs: every forge-cli change in 0.34.0 reads since 0.34.0, and the releases map is refreshed - #274

Merged
fas89 merged 1 commit into
mainfrom
claude/docs-since-0.34.0
Nov 19, 2026
Merged

fas89 merged 1 commit into
mainfrom
claude/docs-since-0.34.0

Conversation

@fas89

@fas89 fas89 commented Nov 19, 2026

Copy link
Copy Markdown
Collaborator

Summary

forge-cli cut its 0.34.0 changelog entry (forge-cli #1020, 127fa5bf on main). The cli-consistency job fetches forge-cli's CHANGELOG.md from main, so since that commit the release-marker sweep in scripts/check_cli_docs.py fails on docs main and on every pull request: a marker that says a pull request is not yet in a release names one that is in 0.34.0. This pull request does what docs/contributing.md asks once work ships.

  • 51 markers of the form *On forge-cli main, not yet in a release ([forge-cli #N](...)).* in 7 pages become *(since 0.34.0, [forge-cli #N](...))*: the pull requests #1007, #1008, #1009, #1010, #1012, #1013, #1014, #1015 and #1017.
  • Three sentences that said "on main" for one of these changes now say 0.34.0 (the key of a dead letter sent to a topic, the argv of a local run, and the dbt trigger output in airflow.md). Statements that an output was produced "on forge-cli main" are left as they are: they say where the output ran.
  • scripts/forge-cli-releases.json is regenerated with python scripts/check_cli_docs.py --refresh-releases <forge-cli checkout> --refresh-ref origin/main, with forge-cli main at 127fa5bf: 64 pull requests mapped, reviewed through 0.34.0.
  • upgrading.md: the section "Not in a release yet" is "Changes in 0.34.0", with an intro like the earlier releases'.

Decisions

  • The pin stays at 0.33.0. docs/.vuepress/cli-version.json names a release that has to install from PyPI, and the pin bump, the regenerated contract reference pages and the clean-up that follow it belong to the pull request of the pin (as docs: forge-cli 0.33.0 (pin, contract reference, upgrade notes) #271 did for 0.33.0). A since 0.34.0 line passes the version sweep with the pin at 0.33.0, as since 0.33.0 did at 0.32.0.
  • Only the markers of pull requests that the refreshed map puts in 0.34.0 were converted; none was skipped. #1018 and #1019 are in 0.34.0 as well, and their docs follow this pull request: they cite those pull requests, so the map picks them up when it is refreshed again.
  • No wording changes beyond the marker form, those three sentences and the intro of the upgrading section.

Checklist

  • python scripts/check_cli_docs.py against the 0.33.0 CLI and the changelog of the cut passes: 0 markers left, 0 pending; check_providers.py and gen_contract_reference.py --check pass
  • Site build, built-link check and offline link check pass locally

Notes

…leases map is refreshed

51 markers of the form on forge-cli main, not yet in a release become since 0.34.0; the section Not in a release yet is Changes in 0.34.0; three sentences that said on main for one of these changes say 0.34.0.

This branch was previously deployed

1 inactive deployment
github-pages — ad3fb9f7 Deployed Nov 19, 2026 by fas89 via deploy #431
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.

1 participant