Conversation
Mirrors the clayterm-crank CI setup: verify on PR/main, publish to npm and jsr on v* tags, and pkg-pr-new previews on PRs.
Annotate NodeContext with Context<NodeImpl> so the public API has explicit types, satisfying jsr's no-slow-types lint.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The repository was moved to
thefrontside/freedomand needs CI/CD on par withthefrontside/clayterm: automatic verification on PRs (including dry runs of both publish pipelines) and tag-driven publishing of@frontside/freedomto npm and jsr.Approach
Mirror clayterm's workflow set, adapted for a single-package, no-wasm repo:
verify.ymlβ on push/PR tomain. Atestjob runsdeno fmt --check,deno lint, anddeno task test. Dependentjsrandnpmjobs then dry-run the publish pipeline against a synthetic0.0.0-verify.0version, so any packaging issue surfaces on the PR rather than at tag time.publish.ymlβ onv*tags. Dry-runs both registries, builds, then publishes to npm (viadnt) and jsr (after stamping the tag version intodeno.json).preview.ymlβ per-PR previews viapkg-pr-new.Two commits:
tasks/build-{npm,jsr}.ts+deno.jsontask wiring +.gitignore.deno fmtreflow + an explicitContext<NodeImpl>annotation onNodeContext(required by jsr'sno-slow-typeslint), so verify is green on landing.Possible Drawbacks or Risks
Publishing requires
NPM_TOKENandJSR_TOKENrepo secrets (or OIDC trust). Not yet configured.TODOs and Open Questions
JSR_TOKENrepo secret