Skip to content

Retire unproduced BanSafe trigger fixtures - #36

Merged
purpshell merged 2 commits into
devfrom
codex/retire-bansafe-event-names-20260923
Sep 26, 2026
Merged

purpshell merged 2 commits into
devfrom
codex/retire-bansafe-event-names-20260923

Conversation

@purpshell

@purpshell purpshell commented Sep 26, 2026 •

Copy link
Copy Markdown
Member

The API no longer produces bansafe.risk_changed, bansafe.health_changed, or bansafe.enforcement, and the SDK no longer offers their test fixtures. Remove the retired trigger example and fixture list from the CLI guidance. Pin the published SDK that rejects those fixture names, and test that the CLI rejects each one before sending a request.

Contract and release impact:

  • API — updated upstream: polymorfa/polymorfa@6839976e retired the three names from the authoritative webhook and Test event contracts (PR #301). No API handler changes occur in this CLI PR.
  • SDKs — updated upstream: polymorfa/sdks@c98cbef73e2f39516b791cef1d02cab4b53bb787 removed the TypeScript fixture and webhook types (PR #298). This CLI pins the inspected npm artifact @polymorfa/sdk@0.1.0-dev.20260926005918 exactly in its manifest and lockfile.
  • CLI — updated here: trigger help and README list only supported fixtures; retired names fail CLI argument validation before transport. Existing BanSafe inspection commands are unchanged.
  • Docs — updated: The API PR updated the Mintlify webhook, BanSafe, Test event, SDK overview, and changelog pages. This PR updates the CLI README examples and version output. No new public route or CLI command is introduced.
  • Feature releases — unaffected here: The existing Test numbers beta release, enrollment, entitlement, and server-side feature checks remain authoritative. This CLI change does not alter a flag or claim deployed availability.

Validation on Node 22: clean npm ci; focused trigger suite (12 passed); npm run verify (format, lint, typecheck, 856 tests across 87 files, build, pack dry run, production audit); runtime polymorfa version reports the pinned SDK. The SDK publish workflow passed for the merged commit, and npm serves the exact version with the dev tag and integrity metadata. No live Test number delivery was exercised.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.

@coderabbitai

coderabbitai Bot commented Sep 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

  • Ask an admin to enable usage-based reviews

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Next included review available in 4 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available. Your 61 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

The included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 6b48f3a8-23c0-4ec2-a7b7-c17fce04f273

📥 Commits

Reviewing files that changed from the base of the PR and between 3ab73ea and d3a94c1.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (4)
  • README.md
  • package.json
  • src/commands/trigger.ts
  • test/commands/trigger.test.ts

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

@purpshell
purpshell merged commit fad2cf7 into dev Sep 26, 2026
3 checks passed
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.

1 participant