Skip to content

feat(stripe-projects): integrate plugin 0.30.0 → 0.31.0 - #100

Open
cursor[bot] wants to merge 1 commit into
mainfrom
bot/stripe-projects-0.31.0
Open

feat(stripe-projects): integrate plugin 0.30.0 → 0.31.0#100
cursor[bot] wants to merge 1 commit into
mainfrom
bot/stripe-projects-0.31.0

Conversation

@cursor

@cursor cursor Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Daily Stripe Projects upgrade. Pin moves from 0.30.0 to 0.31.0.

Version delta

  • Installed latest stripe projects (0.31.0) against main pin 0.30.0.
  • Re-blessed plugin-version.txt, catalog.json, and command-surface.txt via mise run stripe-refresh.
  • Synced STRIPE_PROJECTS_PINNED and the surface TRAVERSAL verification note.
  • No intermediate versions between 0.30.0 and 0.31.0 on this track.
  • No open upgrade PR existed; opened this one on bot/stripe-projects-0.31.0. Left stale remote bot/stripe-projects-update alone (fixtures-only tip, no PR).

Fixture changelog

Catalog (198 services, unchanged set)

  • Still 89 deployables and 109 plans. No added or removed refs. No configuration_schema edits.
  • Description-only noise: posthog/analytics (wording), chatbase/hobby plan (500 → 700 message credits).
  • drift_report stayed empty without catalog.rs changes.

Command surface

  • TRAVERSAL unchanged (no new top-level commands).
  • spend gained optional --duration, --since, and --until date-range flags. Default remains last 6 months.

Landed integrations

  • None. Catalog service set and schemas are unchanged; no new CatalogResource adapters.

Explicit skips

  • Spend date-range flags. spend_summary still calls bare spend / spend <provider> for up/down reporting. Stackless has no CLI that needs duration windows.
  • Plan-tier credit text (chatbase/hobby) stays out of scope with other plan tiers.
  • Pre-existing gaps such as createos/project, domains, containers stay out of scope.
  • No new --on substrates (needs human stripe projects link + live smoke).
  • Live discover skipped (no linked project / OAuth here).

Predicate evidence

  • mise run check green (fmt, clippy, taplo, catalog-orphans, provisional-check).
  • Targeted nextest -p stackless-stripe-projects -p stackless --all-features: 117/117, including fixture coherence and spend_summary_*.
  • Do not merge. Leave for morning review.
Open in Web View Automation 

Note

Low Risk
Fixture and version-pin updates only; no runtime logic changes beyond aligning snapshots with plugin 0.31.0.

Overview
Bumps the Stripe Projects plugin pin from 0.30.0 to 0.31.0 in STRIPE_PROJECTS_PINNED, the surface TRAVERSAL verification note, and plugin-version.txt, and re-blesses catalog.json and command-surface.txt via the usual refresh path.

The catalog snapshot keeps the same service set; changes are mostly reordered allowed_updates / updateable_to lists plus minor copy (e.g. PostHog analytics description, Chatbase hobby 500 → 700 message credits). No new commands in TRAVERSAL.

The notable CLI delta in the command surface is stripe projects spend: new optional --duration, --since, and --until for charge date ranges (default still last 6 months). Stackless spend_summary is unchanged and still invokes bare spend / spend <provider>.

Reviewed by Cursor Bugbot for commit 89a2b80. Bugbot is set up for automated code reviews on this repo. Configure here.

Re-bless plugin-version, catalog, and command-surface against latest.
Sync STRIPE_PROJECTS_PINNED and surface TRAVERSAL verification note.
@vercel

vercel Bot commented Aug 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
stackless Ready Ready Preview Aug 4, 2026 10:10am

@snowmead
snowmead marked this pull request as ready for review August 4, 2026 12:29
@cursor

cursor Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_1e82dd1d-aa7c-4249-b086-6d6d624f6925)

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Thermos review (security + code quality)

NO MEDIUM+ FINDINGS

Both thermo-nuclear passes agree: this is a pin/fixture-only bump of Stripe Projects 0.30.00.31.0. No runtime logic, adapters, authz, secret handling, or TRAVERSAL structural changes.

Validated

  • Pins synced: STRIPE_PROJECTS_PINNED, plugin-version.txt, surface header, and banner all report 0.31.0
  • Catalog: 198 services, 0 add/remove; 2 description-only edits; no configuration_schema content changes
  • New spend --duration/--since/--until flags are optional; help default remains last 6 months; spend_summary still correctly uses bare spend (explicit skip)
  • Hermetic CI green (fmt/clippy/test/supply-chain). Live render/vercel smoke failures are unrelated Render API 201 handling, not this pin

No prior automation review threads. Bugbot hit a usage limit (no Bugbot findings to incorporate).

Open in Web View Automation 

Sent by Cursor Automation: Find vulnerabilities

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