Skip to content

ci(audit-action): fix release trigger to main and bump to 3.2.1#16

Merged
cherviakovtaskworld merged 2 commits into
mainfrom
cherviakovtaskworld/fix-release-workflow-trigger
Jul 3, 2026
Merged

ci(audit-action): fix release trigger to main and bump to 3.2.1#16
cherviakovtaskworld merged 2 commits into
mainfrom
cherviakovtaskworld/fix-release-workflow-trigger

Conversation

@cherviakovtaskworld

Copy link
Copy Markdown
Contributor

The release workflow triggered on pull_request to master, but the
repository's default branch is main, so it never fired — no v3.2.x tag
was ever created despite package.json sitting at 3.2.0. Point the trigger
at main and bump the patch version so the lockfile-closure fix (#15) can
be published.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

The release workflow triggered on pull_request to `master`, but the
repository's default branch is `main`, so it never fired — no v3.2.x tag
was ever created despite package.json sitting at 3.2.0. Point the trigger
at `main` and bump the patch version so the lockfile-closure fix (#15) can
be published.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

Vulnerabilities

Vulnerabilities were found in audit-action.

⚪ Info 0
🔵 Low 2 `>undici@6.25.0`
🟡 Moderate 1 `>undici@6.25.0`
🟠 High 1 `>undici@6.25.0`
🔴 Critical 0

Gate the release step on an output flag instead of letting `grep -q` fail
the job: merges to main that don't bump package.json now skip the release
steps (green) rather than reporting a failed workflow run. Add a
`merged == true` job guard so closed-but-unmerged PRs don't trigger it, and
let workflow_dispatch force a release of the current version.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cherviakovtaskworld
cherviakovtaskworld merged commit 017eb77 into main Jul 3, 2026
1 check passed
@cherviakovtaskworld
cherviakovtaskworld deleted the cherviakovtaskworld/fix-release-workflow-trigger branch July 3, 2026 07:30
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