@dotcms/uve 26.8.7-1 → 26.8.10-1-next.2504

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 +26 -4
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -169,11 +169,33 @@ To make the layout editable, be sure to apply all required `data-dot-*` attribut
169
169
 
170
170
  ### Get a dotCMS Environment
171
171
 
172
- #### Version Compatibility
172
+ #### Which SDK Version Should I Use?
173
173
 
174
- - **Recommended**: dotCMS Evergreen
175
- - **Minimum**: dotCMS v25.05
176
- - **Best Experience**: Latest Evergreen release
174
+ dotCMS SDKs are published in lockstep with dotCMS itself: every `@dotcms/*` package ships
175
+ at the **exact same version number** as the dotCMS release it was built for (e.g. dotCMS
176
+ `26.7.14-1` `@dotcms/client@26.7.14-1`, `@dotcms/react@26.7.14-1`, and so on).
177
+
178
+ **Simple rule of thumb: use the SDK version that matches your dotCMS instance's version.**
179
+
180
+ You don't have to upgrade the SDK every time dotCMS releases a new version (or vice versa).
181
+ Most releases don't change anything the SDKs rely on, so an older SDK usually keeps working
182
+ fine against a newer dotCMS instance. Occasionally, though, a release does include a real
183
+ breaking change — and if your SDK is older than that point, it will stop working correctly.
184
+
185
+ You don't need to track this yourself: your dotCMS instance always knows the oldest SDK
186
+ version it still supports, and the SDK checks itself against it automatically. If you're
187
+ using an SDK that's too old, you'll see a clear warning in your console telling you to
188
+ upgrade.
189
+
190
+ **Recommendation:** pin your SDKs to the same version as your dotCMS instance, and only bump
191
+ them when you upgrade dotCMS — or when the console tells you to.
192
+
193
+ > **On an LTS release?** LTS releases don't currently get their own matching SDK version.
194
+ > Until that's addressed, use the SDK version published for the closest regular release at
195
+ > or before your LTS version.
196
+ >
197
+ > Want more background on how dotCMS releases and support windows work? See
198
+ > [Release & Support Lifecycle](https://dev.dotcms.com/docs/release-support-lifecycle).
177
199
 
178
200
  #### Environment Setup
179
201
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dotcms/uve",
3
- "version": "26.08.07-01",
3
+ "version": "26.8.10-1-next.2504",
4
4
  "description": "Official JavaScript library for interacting with Universal Visual Editor (UVE)",
5
5
  "repository": {
6
6
  "type": "git",