Skip to content

Prepare the coordinated 2.1.0 release - #258

Merged
nicklambourne merged 79 commits into
masterfrom
codex/release-2-1
Aug 14, 2026
Merged

Prepare the coordinated 2.1.0 release#258
nicklambourne merged 79 commits into
masterfrom
codex/release-2-1

Conversation

@nicklambourne

@nicklambourne nicklambourne commented Aug 13, 2026

Copy link
Copy Markdown
Owner

Scope

Bumps both language packages to 2.1.0, refreshes the Python lockfile and installation guidance, and adds language-specific release notes. It does not create tags or publish packages.

Stack

  • Train: 2.1 feature and release
  • Step: 7 of 7
  • Base: codex/ci-validation
  • This is a stacked draft for isolated review.
  • After the predecessor is merged, retarget this PR to master before merging it.

Validation

492 Python tests at 94.78 percent coverage, mypy, Ruff, wheel/sdist and Twine checks; 206 TypeScript tests, typecheck, package and npm tarball checks; and the full Docusaurus/API-reference build passed locally.

Follow-on documentation archive

The historical Docusaurus archive continues as the draft train #259 through #264. PR #259 records this PR final base as a188c2c; the follow-on train remains unmerged and does not deploy or modify gh-pages.

Nicholas Lambourne and others added 25 commits August 14, 2026 15:31
The docs-example test resolves the package by name at runtime, and the
docs build sets its own UV_CACHE_DIR so the setup-uv cache post-step
fails on an empty cache path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@nicklambourne
nicklambourne marked this pull request as ready for review August 14, 2026 12:59
@nicklambourne
nicklambourne changed the base branch from codex/ci-validation to master August 14, 2026 12:59
@nicklambourne
nicklambourne merged commit 00298c8 into master Aug 14, 2026
21 checks passed
@nicklambourne
nicklambourne deleted the codex/release-2-1 branch August 14, 2026 13:35
nicklambourne added a commit that referenced this pull request Aug 17, 2026
* chore: move Python package into workspace

* test: establish shared conformance contract

* feat: add TypeScript package

* ci: add coordinated package release automation

* docs: migrate site to Docusaurus

* feat: make docs language selection site-wide

* docs: complete language-specific guides

* feat: expose versioned documentation

* feat: standardise TypeScript block factory names

* docs: improve API reference generation and navigation

* test: enforce comprehensive conformance coverage

* feat: support current Block Kit blocks in Python

* feat: support current Block Kit blocks in TypeScript

* docs: bring TypeScript API reference to parity

* docs: add validated Block Kit previews

* ci: align monorepo validation

* chore: prepare 2.1.0 release

* ci: give stacked pull requests check runs

Run push-triggered workflows only for master (PR branches already get
pull_request runs, and stacked branches previously got neither), and drop
the pull_request branches filter so pull requests targeting stacked train
branches receive checks before they are retargeted to master.


* ci: give stacked pull requests check runs


* ci: give stacked pull requests check runs


* ci: build the smoke package before switching to the matrix Node

pnpm 11.16 requires Node 22.13+, so the Node 20.19 smoke leg must install
and build under the runner's default Node and only then switch versions
for the import checks.


* ci: pin setup-uv to an existing tag

astral-sh/setup-uv publishes no moving v10 tag, so the docs workflow
could not resolve its action.


* ci: alias the package name for docs-example typechecking

The docs-example test imports docs/examples/typescript/section_hello.ts,
which imports the package by name; tsc needs the same alias vitest uses.


* ci: resolve the package alias in vitest and skip the unused uv cache

The docs-example test resolves the package by name at runtime, and the
docs build sets its own UV_CACHE_DIR so the setup-uv cache post-step
fails on an empty cache path.


---------
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