Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,6 @@
"version": "0.2.0",
"description": "Kernel CLI: a repo-local quality system and portable operating layer for coding agents.",
"type": "module",
"private": true,
"license": "Apache-2.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update release-readiness expectations before publishing

In the npm-release workflow I inspected, the job runs pnpm test before the publish gate (.github/workflows/npm-release.yml), and tests/release-readiness.test.ts:169 still asserts packageJson.private is true. With private removed here, the release job and CI test step fail before reaching npm publish, so the 0.2.0 publication bootstrap cannot complete until the readiness test/checklist are updated for the non-private release state.

Useful? React with 👍 / 👎.

"repository": {
"type": "git",
Expand Down
6 changes: 5 additions & 1 deletion tests/release-readiness.test.ts
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,11 @@ describe('Kernel release-readiness workflow', () => {

expect(packageJson.name).toBe('@mattbaconz/kernel');
expect(packageJson.license).toBe('Apache-2.0');
expect(packageJson.private).toBe(true);
if (packageJson.private === true) {
expect(packageJson.private).toBe(true);
} else {
expect(packageJson.private).toBeUndefined();
}
expect(packageJson.bin).toEqual({
kernel: './dist/cli/index.js'
});
Expand Down