Skip to content

chore(release): bump to v0.8.3#149

Merged
Raftersecurity merged 2 commits into
mainfrom
sable-release-0.8.3
May 31, 2026
Merged

chore(release): bump to v0.8.3#149
Raftersecurity merged 2 commits into
mainfrom
sable-release-0.8.3

Conversation

@Rome-1

@Rome-1 Rome-1 commented May 31, 2026

Copy link
Copy Markdown
Collaborator

Summary

Cuts v0.8.3. Headline change: the github-action/ cloud variant's severity-threshold default flips from high to none so first installs no longer break CI on day one (#148). All four version sites bumped (node/package.json, python/pyproject.toml, both rafter-security-skill.md frontmatter copies) — validate-release.yml enforces parity. CHANGELOG entry added.

How this ships

Standard prod-branch flow:

  1. This PR merges to main.
  2. Someone (with prod-merge rights) merges mainprod.
  3. publish.yaml fires on the prod push: tests → npm Trusted Publishing → PyPI (--skip-existing) → ClawHub → GitHub Release tagged v0.8.3 → smoke-tests against the live registries.
  4. The GitHub Release with tag v0.8.3 is what GitHub Marketplace picks up to republish the root /action.yml listing entry.

Contents of this release (since v0.8.2)

User-facing:

Infrastructure:

Test plan

  • validate-release.yml (this PR's CI) passes — version parity + CHANGELOG entry present.
  • After merge to main + promotion to prod: publish.yaml succeeds end-to-end, v0.8.3 tag created, GitHub Release rendered, npm + PyPI smoke-tests pass.
  • npm view @rafter-security/cli@0.8.3 and pip index versions rafter-cli show 0.8.3 within ~3 minutes of publish.
  • Workflow consumer of Raftersecurity/rafter-cli/github-action@main with no severity-threshold set → scan runs, PR comment + SARIF emitted, build does not fail.

🤖 Generated with Claude Code

Rome-1 and others added 2 commits May 31, 2026 07:28
Headline change in this release is github-action/ cloud variant
default-flip from severity-threshold: high to severity-threshold:
none (report-only). See CHANGELOG.md for the full entry and the
infrastructure improvements that accumulated since 0.8.2.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Three pure-bash test scripts exercise the exact code paths touched by
the severity-threshold: high -> none default flip:

- test-threshold-eval.sh: 30 assertions across all 6 threshold values
  (critical/high/medium/low/none/unknown-fallback) and finding-count
  permutations. Confirms 'none' never fails the build regardless of
  findings, and that critical/high/medium/low still fail as before.

- test-pr-comment-tip.sh: 9 assertions on the new report-only-tip
  block. Confirms the tip appears exactly when (findings > 0) AND
  (threshold == 'none').

- test-action-yml-defaults.sh: drift detector. Asserts (1) the
  severity-threshold default is literally 'none', (2) the env var
  passthrough on the Comment-on-PR step is intact (the GitHub-recommended
  template-injection mitigation), (3) the tip block is gated on both
  conditions, (4) the 'none' branch of the threshold-eval doesn't set
  FAIL=1. Each check independently verified against a mutated copy of
  action.yml.

Wired into a new test-github-action.yml workflow that runs on PRs +
main pushes touching github-action/**. The Rafter API is not exercised
here; that's a future addition that would need an injectable
RAFTER_API_KEY secret and a fixture repo.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@Raftersecurity
Raftersecurity merged commit 578db09 into main May 31, 2026
4 checks passed
@Raftersecurity
Raftersecurity deleted the sable-release-0.8.3 branch May 31, 2026 22:42
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