Skip to content

ci: add workflow_dispatch and build step to npm-publish#86

Merged
TonyCasey merged 1 commit into
mainfrom
release-prep
Feb 16, 2026
Merged

ci: add workflow_dispatch and build step to npm-publish#86
TonyCasey merged 1 commit into
mainfrom
release-prep

Conversation

@TonyCasey
Copy link
Copy Markdown
Owner

Summary

  • Add workflow_dispatch trigger to restore the manual "Run workflow" button on GitHub Actions
  • Add missing npm run build step before npm publish

Test plan

  • Verify workflow YAML is valid
  • After merge, confirm "Run workflow" button appears on the Actions page

🤖 Generated with Claude Code

Copilot AI review requested due to automatic review settings February 16, 2026 11:18
@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Feb 16, 2026

Caution

Review failed

The head commit changed during the review from ac3d3ba to 194fc43.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release-prep

Comment @coderabbitai help to get the list of available commands and usage tips.

Restores the manual "Run workflow" button on GitHub Actions page.
Also adds missing `npm run build` step before publish.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
AI-Agent: Claude-Code/2.1.42
AI-Model: claude-opus-4-6
AI-Decision: The npm publish workflow should run 'npm run build' after 'npm ci' but before 'npm publish' to ensure built artifacts are included in the published package.
AI-Confidence: high
AI-Tags: ci-cd, npm-publish, build-process, github-actions, workflow-dispatch, manual-trigger, build-order
AI-Lifecycle: project
AI-Memory-Id: c15bde7d
AI-Source: llm-enrichment
@TonyCasey TonyCasey merged commit b273e4f into main Feb 16, 2026
1 check passed
@TonyCasey TonyCasey deleted the release-prep branch February 16, 2026 11:19
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR introduces a dedicated GitHub Actions workflow for manual / release-triggered npm publishing, and updates project docs and metadata to reflect recent feature additions (multi-provider LLM support, new CLI commands, and new hooks).

Changes:

  • Add .github/workflows/npm-publish.yml with workflow_dispatch and an explicit npm run build before npm publish.
  • Update docs/README/CLAUDE.md/CHANGELOG.md content around trailers, hooks, and multi-provider LLM configuration.
  • Adjust an integration test to use GIT_MEM_MODEL instead of ANTHROPIC_MODEL under CLAUDECODE.

Reviewed changes

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
tests/integration/hooks/hook-commit-msg.test.ts Makes model detection test more stable by using higher-priority GIT_MEM_MODEL.
package.json Updates package version/description (but conflicts with semantic-release flow).
docs/getting-started.md Expands docs for trailers and multi-provider LLM configuration / env vars.
README.md Adds an image to the README.
CLAUDE.md Updates architecture/entrypoint documentation to reflect new commands and hook handlers.
CHANGELOG.md Updates release notes for 0.5.0 and adds new bullets.
.github/workflows/npm-publish.yml Adds a publish workflow with manual trigger and build-before-publish.
Comments suppressed due to low confidence (2)

.github/workflows/npm-publish.yml:20

  • Repo workflows consistently use Node.js 22 (ci.yml, release-on-merge.yml). This workflow pins Node 20 and also omits the cache: 'npm' setting used elsewhere, which increases CI time and can hide Node-version-specific issues. Align node-version with the rest of the repo and enable npm caching via setup-node.
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - run: npm ci
      - run: npm test

.github/workflows/npm-publish.yml:2

  • The header comment says this publishes to GitHub Packages, but the job config uses the npm registry (registry-url: https://registry.npmjs.org/) and runs npm publish. Update the comment to avoid confusion about where artifacts are being published.
# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 7 to 10
release:
types: [created]
workflow_dispatch:

Copy link

Copilot AI Feb 16, 2026

Choose a reason for hiding this comment

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

This workflow triggers on release: created, but the repo already publishes via semantic-release on push to main (release-on-merge.yml) and creates GitHub releases. When semantic-release creates a release, this workflow will also run and attempt a second npm publish, which will likely fail (version already published) and adds operational noise. Consider removing the release trigger and keeping only workflow_dispatch, or otherwise ensure it won’t double-publish (e.g., guard conditions / use a different registry or artifact source).

Suggested change
release:
types: [created]
workflow_dispatch:
workflow_dispatch:

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants