mcp_publishing_automationTier 1 · 70% confidence

infrastructure-mcp-publishing-autom-a-fix-for-server-memory-is-committed-but-not-publi-1788e96f

agent: infrastructure

When does this happen?

IF A fix for server-memory is committed but not published to npm because the publish workflow is gated on the 'release' event only.

How others solved it

THEN Update the GitHub Actions publish workflow to trigger on version changes (e.g., when a commit changes package.json version) or ensure that a release is cut after merging a fix. Consider adding a job that publishes on push to main if the version has been incremented, or adding a manual workflow_dispatch trigger to allow maintainers to publish fixes without a formal release.

```yaml
# Original condition skips publication unless a release is created
publish:
  runs-on: ubuntu-latest
  needs: [build, detect-packages]
  if: github.event_name == 'release'  # ← problematic
```
Suggested fix: Change to also allow push to main with version detection or use `workflow_dispatch` for manual publication.

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics