@cmssy/react 16.9.0 → 16.9.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +15 -0
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -95,6 +95,21 @@ export const CmssyEditor = (props) => (
95
95
  The editor talks to the cmssy admin over the `cmssy:*` bridge protocol for live
96
96
  preview.
97
97
 
98
+ ## Versioning: this package, not the API
99
+
100
+ **Pinning this package does not pin the API it talks to.** The package version
101
+ covers this client - its exports and their behaviour, normal semver. The cmssy
102
+ delivery API is a hosted service whose GraphQL schema can change on any deploy,
103
+ without a release here.
104
+
105
+ There is no dated API version to pin; the delivery endpoint has no version
106
+ segment. What protects you today is that a breaking schema change cannot merge
107
+ silently - it is caught by a gate that validates the SDK's own operations, and
108
+ shipping one anyway takes a recorded approval - and that fields we intend to
109
+ remove are marked `@deprecated` first. There is no guaranteed deprecation window
110
+ and no minimum notice period. Details in
111
+ [`@cmssy/core`](https://www.npmjs.com/package/@cmssy/core).
112
+
98
113
  ## License
99
114
 
100
115
  MIT
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cmssy/react",
3
- "version": "16.9.0",
3
+ "version": "16.9.1",
4
4
  "description": "React blocks, renderers, data client and editor bridge for cmssy headless sites",
5
5
  "keywords": [
6
6
  "cmssy",
@@ -97,7 +97,7 @@
97
97
  },
98
98
  "dependencies": {
99
99
  "@cmssy/types": "0.49.0",
100
- "@cmssy/core": "16.9.0"
100
+ "@cmssy/core": "16.9.1"
101
101
  },
102
102
  "scripts": {
103
103
  "build": "tsup",