Conversation
…ence Initialize the .knowledge directory as an OKF bundle covering the system overview, component model, runtime and deployment architecture, key architectural decisions (cloud provider abstraction, image-mirror CD, runtime distribution, SDK generation from OpenAPI), API contract constraints, and a development/verification runbook. All content is reconstructed from evidence in the repository rather than assumptions, so future engineers and agents can quickly orient themselves in the codebase.
…on docs Add sdk-publish GitHub Actions workflow and document the development and verification process in the runbook. Update CONTRIBUTING.md to reflect the new publishing flow and record progress in the knowledge log.
Resolve pnpm-lock.yaml conflict by regenerating from the merged workspace manifests: keeps this branch's sdk/js toolchain resolutions (vitest 3.2.x, @types/node ^24) and upstream's website dependencies (rspress 2.0.21) re-resolved on top.
|
Resolved the conflict with the latest What conflicted: How it was resolved: rather than hand-editing the lockfile, I started from this branch's side (preserving the tested Verification on the merged tree:
|
|
@songhn233 , could you please review my PR? Thank you |
1 participant
Summary
Three focused commits on top of
main:1.
57549c9— docs: add OKF knowledge base reconstructed from repository evidenceInitializes the
.knowledgedirectory as an OKF bundle covering the system overview, component model, runtime and deployment architecture, key architectural decisions (cloud provider abstraction, image-mirror CD, runtime distribution, SDK generation from OpenAPI), API contract constraints, and a development/verification runbook. All content is reconstructed from evidence in the repository rather than assumptions, so future engineers and agents can quickly orient themselves in the codebase.2.
144fc2b— ci: add SDK publishing workflow and expand development docsAdds the
sdk-publishGitHub Actions workflow (manual dispatch; version bump + npm/PyPI publish with dry-run support, committing the bump back) and documents the development and verification process in the runbook. UpdatesCONTRIBUTING.mdto reflect the new publishing flow.3.
adfafb6— chore(ci): support Node 24; test matrix [20, 24], vitest 1→3, engines >=20sdk-ci.ymlruns the JS SDK build/tests on a Node [20, 24] matrix withfail-fast: false(backward-compat checks per maintainer decision);sdk-publish.ymlbuilds/publishes on Node 24engines.noderaised from>=18.0.0to>=20.0.0— supported window is now the last three LTS lines (20, 22, 24).@types/nodebumped to^24in root/website/sdk-js/examples manifests (dev-only)^3.2.4) because Vitest 1.x does not support Node 24Test plan
pnpm build && pnpm testinsdk/js— 66 tests pass, 16 skipped, on both Node 20 (vitest 1.6.1 baseline) and Node 24 (vitest 3.2.7)tscd.ts output diff vs. baseline is empty@types/nodebump)Notes