Skip to content

release: publish the 2.1.0 documentation - #550

Merged
MaksymStoianov merged 2 commits into
mainfrom
develop
Sep 23, 2026
Merged

MaksymStoianov merged 2 commits into
mainfrom
develop

Conversation

@MaksymStoianov

Copy link
Copy Markdown
Member

Brings fix/writerside-cfg-version (#549) to main, which is where the docs workflow builds and deploys the site.

The merge of #542 left main failing: release-please had bumped the version to 2.1.0 while the five generated writerside.cfg still named 2.0.0, so the generated job stopped the run before anything was built. The documentation for 2.1.0 has not been published yet; this merge is what publishes it.

Closes #548

🤖 Generated with Claude Code

MaksymStoianov and others added 2 commits September 23, 2026 23:54
`writerside.cfg` is generated for each of the five languages and repeats
the version from `package.json`. `release-please` bumped the version and
knew nothing about those files, so the moment a release landed on `main`
the configurations named the previous release and `docs:check` failed the
`docs` workflow before it could build anything. That is how the site for
2.1.0 went unpublished.

The version line now ends with an `x-release-please-version` annotation
and the five files are listed as `extra-files`, so the release pull
request rewrites them along with `package.json`. The annotation sits on
the instance line alone; the `ihp` schema version above it is left as it
is.

Closes #548

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@MaksymStoianov
MaksymStoianov merged commit 8cc5219 into main Sep 23, 2026
16 checks passed
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: every release leaves writerside.cfg behind and fails the docs workflow

1 participant