breaking-changes Cursor ruleA
breaking-changes from reactive/data-client is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add reactive/data-client/.cursor/rules/breaking-changes.mdc@git:20261017.9abb86aPins git:20261017.9abb86a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- reactive/data-client
- Path
.cursor/rules/breaking-changes.mdc- Versions recorded
- 2
- Latest version
- git:20261017.9abb86a, committed Oct 17, 2026
- First version recorded
- Oct 4, 2026
- Size
- 4,003 bytes
- Repository stars
- 2,040
- License
- Apache-2.0
Strategy for type/API changes that would break users or mixed package versions.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Breaking Change Strategy Get users the fix now with a clean upgrade path; batch the actual break into a later release. ## Before shipping a change that could break Check both: - **User code**: subclasses, overrides, explicit annotations, and classes implementing exported interfaces. - **Mixed versions**: `@data-client/rest`/`endpoint`/`graphql` aren't dependencies of `react`/`vue`/`core`, so users can pair a newer client with an older endpoint (and vice versa). Type checks in core against endpoint types must still accept older endpoint versions. Requiring a matching version for a feature that is new in the same release is not breaking. ## When it would break 1. **Ship a compatible version**: a shim that keeps old code compiling and working (e.g. method-syntax declarations for parameter bivariance, a loose structural type instead of the strict interface, a deprecated alias). 2. **Prepare users**: in the changeset and the release's draft blog post, recommend the future-proof form now with a code example, so the later break is a no-op for them. …
Read the whole file at its exact version.
How to install
mdr add reactive/data-client/.cursor/rules/breaking-changes.mdc@sha256:232c7067a562fb46The line at the top of this page pins the label git:20261017.9abb86a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ykkhfzwf6zwvgu4c)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 4, 2026 and Oct 17, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.9abb86a latest | 2026-10-17 | 9abb86a | 4,003 B | A | view · diff |
| git:20261004.cc57a77 | 2026-10-04 | cc57a77 | 1,707 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (4003 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
reactive/data-client · 2,040 stars · license Apache-2.0 · pushed 2026-11-01 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_ykkhfzwf6zwvgu4c GET https://markdownregistry.com/api/v1/resolve?ref=reactive/data-client/.cursor/rules/breaking-changes.mdc GET https://markdownregistry.com/api/v1/blob/232c7067a562fb46f3c6b42cdb62c81eaa73723944b02e38a33e8de988dd1545
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.
More from reactive/data-client
Every file in reactive/data-client