feat(reunite): switch to next realm and theme versions#7
Conversation
There was a problem hiding this comment.
cafe AI Review: 🟢 Completed
Reunite Agent has reviewed your changes and found 2 potential issue(s).
Note
Low Risk
Changes dependency tags for @redocly/realm and @redocly/theme from latest to next. The risk is low as this primarily impacts the documentation build and preview environments for the Cafe API, though it introduces pre-release versions of these packages.
Overview
Updates package.json to switch the @redocly/realm and @redocly/theme dependency versions from latest to next, enabling the project to use the upcoming versions of the Redocly Realm and Theme packages. Also includes the corresponding updates to package-lock.json.
| "@redocly/realm": "latest", | ||
| "@redocly/theme": "latest" | ||
| "@redocly/realm": "next", | ||
| "@redocly/theme": "next" |
There was a problem hiding this comment.
Switching to the next tag introduces pre-release versions. This risks pulling in unstable features or breaking changes. Verify this is the intended strategy for this project.
| "@redocly/realm": "latest", | ||
| "@redocly/theme": "latest" | ||
| "@redocly/realm": "next", | ||
| "@redocly/theme": "next" |
There was a problem hiding this comment.
Only root dependencies were updated. The resolved package versions lower in the file remain unchanged. Run npm install to fully update the lockfile and avoid inconsistent dependency resolution.
Switched from
latesttonextrealm and theme versions for Cafe API