Conversation
Share one versioned result between CLI JSON, Action JSON, and saved reports. Publish its schema and TypeScript types with the npm package. Keep completion status independent of advisory Action step outcomes. BREAKING CHANGE: Action JSON wraps findings in diagnostics. Action JSONL uses the canonical diagnostic fields and exclusive end positions.
Update runner and Docker assertions for the result object. Keep the manual example checked against real CLI output and clarify result docs.
- Centralize tool versions (Go, Node, Pandoc) in workflow `env` - Upgrade `runner-run` to v0.26.2 and Node.js to v26.8.2 - Refactor `package.json` scripts to use `runner` for workspace tasks - Parallelize setup and build steps in `pages.yml` - Remove `comment-cop` from Makefile in favor of npm scripts - Add `.npmrc` to allow git operations from root
- Bump @kjlint/changelog-rss to v0.0.3 in playground - Add "source" field to package exports in changelog-feed - Configure Vite and TypeScript to resolve "source" conditions - Clean up importmap and vite-ignore comments in playground HTML
Allow npm to install the declared Git dependency and typecheck the Action and release test scripts exercised by the new JavaScript job. Keep npm test available through the explicit test:js aggregate.
kjanat
added
documentation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Expand package metadata consistently across the workspace and declare Node/npm development requirements for the GitHub Action package. Update dprint plugins and align the checks documentation formatting.
Build release-triggered Pages deployments from the default branch so maintenance releases cannot redeploy an older checkout. Preserve the triggering commit for pushes and manual runs.
kjanat
changed the title
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2cf1ae998a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| run playground:make:build | ||
| run playground:preview |
There was a problem hiding this comment.
In a fresh checkout, installing this repository's npm dependencies places the runner-run executable in node_modules/.bin but does not expose a bare run command in the contributor's shell; only the workflows install it onto PATH via kjanat/runner. These prescribed local checks therefore fail with run: command not found unless contributors independently install extra global tooling. Use the existing root npm scripts (or npm exec) so the documented validation works from a normal project install.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
add to mise: [tool] runner-run = "latest" with [tool_alias] runner-run = "github:kjanat/runner"
This branch has not been deployed
1 participant
The changelog page now bundles the reader from the checked-out workspace. Its dependency previously selected a nested registry copy of 0.0.0 while the browser loaded 0.0.3 separately from a CDN. Source exports, Vite/TypeScript resolution and the lockfile now agree on the local package. The build verifies the resolved reader belongs to this checkout, catching future version-range drift.
Sixth stack layer, based on #201; follows #182, #183, #184 and #185.
test:jsaggregate, retainingnpm test, the existing development commands, Biome coverage and the Node 24 Action checks.Validation: clean npm installation;
runner install --frozen test:js; playground build and tests; lint and typechecks; Action workspace tests and built entrypoint tests; focused release-script tests; workflow lint with ShellCheck; formatting and Comment Cop. The built site source map contains the workspace reader, and its HTML no longer contains the external package import map.