Skip to content

Revert info.version to 2025-10-13 and document version-bump rule - #678

Closed
ls-bolt[bot] wants to merge 1 commit into
mainfrom
07-10-grid-version-revert-2025-10-13
Closed

Revert info.version to 2025-10-13 and document version-bump rule#678
ls-bolt[bot] wants to merge 1 commit into
mainfrom
07-10-grid-version-revert-2025-10-13

Conversation

@ls-bolt

@ls-bolt ls-bolt Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

This PR has been claimed. The active PR is now #679.

Summary

  • Revert the Grid API OpenAPI info.version from 2026-06-29 back to 2025-10-13, the value it held on the initial schema commit. Edited the source openapi/openapi.yaml and rebundled (make build), so the generated openapi.yaml and mintlify/openapi.yaml are updated in lockstep.
  • Add a Critical Rules bullet to CLAUDE.md establishing the versioning convention: bump info.version only when a breaking change ships, at which point it should match a new servers.url path.

Why

The two prior bumps (#617: 2025-10-132026-06-25, and #633: 2026-06-252026-06-29) were both purely additive, non-breaking schema changes. Under the new convention the version should not have moved for those, so it's reset to 2025-10-13 — which matches the current servers.url path https://api.lightspark.com/grid/2025-10-13.

Test plan

  • make lint passes (0 errors).
  • Verified info.version reads 2025-10-13 in all three files (openapi/openapi.yaml, openapi.yaml, mintlify/openapi.yaml).

Requested by @shreyav

Slack thread: https://lightsparkgroup.slack.com/archives/D0AH5T8FMGE/p1783708971530589


🤖 custodial-circuit(#1) | Feedback

Set the OpenAPI spec info.version back to the initial 2025-10-13 and add a
Critical Rules bullet: bump info.version only on a breaking change, matching a
new servers.url path.
@vercel

vercel Bot commented Jul 10, 2026

Copy link
Copy Markdown

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

2 Skipped Deployments
Project Deployment Actions Updated (UTC)
grid-flow-builder Ignored Ignored Preview Jul 10, 2026 6:59pm
grid-wallet-demo Ignored Ignored Preview Jul 10, 2026 6:59pm

Request Review

@ls-bolt ls-bolt Bot added the bolt label Jul 10, 2026

akanter commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

This stack of pull requests is managed by Graphite. Learn more about stacking.

@shreyav shreyav closed this Jul 10, 2026
shreyav added a commit that referenced this pull request Jul 10, 2026
## Summary
- Revert the Grid API OpenAPI `info.version` from `2026-06-29` back to
`2025-10-13`, the value it held on the initial schema commit. Edited the
source `openapi/openapi.yaml` and rebundled (`make build`), so the
generated `openapi.yaml` and `mintlify/openapi.yaml` are updated in
lockstep.
- Add a Critical Rules bullet to `CLAUDE.md` establishing the versioning
convention: **bump `info.version` only when a breaking change ships, at
which point it should match a new `servers.url` path**.

## Why
The two prior bumps
([#617](#617):
`2025-10-13` → `2026-06-25`, and
[#633](#633): `2026-06-25`
→ `2026-06-29`) were both purely additive, non-breaking schema changes.
Under the new convention the version should not have moved for those, so
it's reset to `2025-10-13` — which matches the current `servers.url`
path `https://api.lightspark.com/grid/2025-10-13`.

## Test plan
- `make lint` passes (0 errors).
- Verified `info.version` reads `2025-10-13` in all three files
(`openapi/openapi.yaml`, `openapi.yaml`, `mintlify/openapi.yaml`).

Requested by @shreyav

Slack thread:
https://lightsparkgroup.slack.com/archives/D0AH5T8FMGE/p1783708971530589

---
🤖
[custodial-circuit](https://zeus.dev.dev.sparkinfra.net/#/arc?id=custodial-circuit)[(#1)](https://zeus.dev.dev.sparkinfra.net/#/instance?id=custodial-circuit)
| [Feedback](https://zeus.dev.dev.sparkinfra.net/feedback)

Original PR: #678
@shreyav
shreyav deleted the 07-10-grid-version-revert-2025-10-13 branch July 10, 2026 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants