Repository navigation
docs: record v0.2.0 as released; npm still pending - #2
Conversation
- PROJECT_STATUS.md: phase Released; add release, merge-commit, clean-install and tag-workflow evidence; record the npm blocker (ENEEDAUTH, no NPM_TOKEN). - README.md: note that 0.2.0 is not on npm yet and point at the checkout/directory install path until it is.
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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fc8345fc80
ℹ️ 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".
| > **0.2.0 is not yet on npm.** Until it is published, install it from the | ||
| > repository or a local checkout — see | ||
| > [Loading from a directory or a checkout](#loading-from-a-directory-or-a-checkout) | ||
| > below. The `plugins` entry above resolves once the package is published. |
There was a problem hiding this comment.
For a user installing while 0.2.0 is absent from npm, this fallback is not actionable: the linked section gives neither a clone/tag command nor a complete plugins configuration using the checkout, while the only complete example still names the unpublished npm package. The OpenCode V2 plugin documentation supports explicit local paths and Git package specifications, so provide one exact end-to-end example; otherwise users can retain the unresolved package entry and unknowingly run without the protection this plugin provides.
Useful? React with 👍 / 👎.
| 1. Merge the release pull request for `feat/stranger-danger-v2-hardening` into `master`. | ||
| 2. Create the `v0.2.0` annotated tag and the GitHub release. | ||
| 3. When credentials exist, publish `@gitdamnit/stranger-danger@0.2.0` to npm and verify a clean install. | ||
| 1. To publish to npm: create/claim the `@gitdamnit` scope, authenticate (`npm login`, or set the `NPM_TOKEN` repository secret), then re-run the `publish.yml` workflow for tag `v0.2.0` (or run `npm publish --access public` from a clean checkout of the tag). `publishConfig.access` is already `public` and `prepublishOnly` gates on typecheck, lint, tests, and build. |
There was a problem hiding this comment.
When the maintainer follows the manual alternative from a fresh checkout, npm publish --access public invokes this package's prepublishOnly script before publishing, but the required dev dependencies have not been installed. I reproduced this from an archive of the target commit: npm publish --dry-run --access public exits during npm run typecheck because dependencies such as @types/node and @opencode/plugin are unavailable. npm documents that prepublishOnly runs first for npm publish, so this path should include npm ci before the publish command.
Useful? React with 👍 / 👎.
1 participant
Post-release documentation truth-up for v0.2.0. Documentation only — no code, tests, or build changes.
What changed
PROJECT_STATUS.md: phaseReleased; adds the merge commit, GitHub release URL, clean-install result, and tag-workflow evidence; records the npm blocker (ENEEDAUTH, noNPM_TOKEN).README.md: notes that 0.2.0 is not yet on npm and points at the checkout/directory install path until it is.Why
v0.2.0 is published on GitHub (tag
v0.2.0→ merge commitb634ce5), so the previous status (In Progress) is now inaccurate. The README's npm install form cannot work until the package is published, so it carries an explicit caveat.Evidence
9cfd813542;prodoc validateandprodoc checkpass.