Skip to content

chore: Ci/GitHub actions#1

Merged
ebuildy merged 15 commits into
mainfrom
ci/github-actions
Jun 28, 2026
Merged

chore: Ci/GitHub actions#1
ebuildy merged 15 commits into
mainfrom
ci/github-actions

Conversation

@ebuildy

@ebuildy ebuildy commented Jun 28, 2026

Copy link
Copy Markdown
Owner

No description provided.

ebuildy and others added 9 commits June 28, 2026 11:56
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

ebuildy and others added 6 commits June 28, 2026 13:19
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The CJS build require()d pure-ESM deps (unified, remark-*, rehype-*). Under
Node >=20.19 / >=22 (require(ESM) enabled, as in CI), esbuild interop returned
the module namespace { default: fn } instead of the default export, so
unified().use() threw 'Expected usable value but received an empty preset' and
the Docusaurus e2e build failed. Passed locally only because older Node could
not require() the ESM deps and fell back to the ESM build.

Drop the cjs tsup format and the require export condition (default now points at
the ESM build). Add test/packaging.test.ts to guard against reintroducing a CJS
build. Verified the e2e passes both with and without --experimental-require-module.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Docusaurus 3 (@docusaurus/core) requires Node >=20, so the e2e build cannot run
on Node 18 (verified in a node:18 container: unit tests pass but docusaurus build
fails). Update the CI matrix to [20, 22, 24], add engines.node >=20, and refresh
the Node version references in the docs. Verified the full suite (incl. e2e) on
Node 24 in a container.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
nvm preloaded with Node 20/22/24 (default 20); switch with e.g. `nvm use 22`.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@ebuildy ebuildy merged commit 4a316c8 into main Jun 28, 2026
7 of 8 checks passed
@ebuildy ebuildy deleted the ci/github-actions branch June 28, 2026 13:01
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.

2 participants