Skip to content

doc/update: Added Compatibility matrix#240

Open
1307-Dev wants to merge 5 commits into
mainfrom
compatibility-matrix
Open

doc/update: Added Compatibility matrix#240
1307-Dev wants to merge 5 commits into
mainfrom
compatibility-matrix

Conversation

@1307-Dev
Copy link
Copy Markdown
Collaborator

💡 What is the current behavior?

Compatibility matrix with peer dependencies and version recommendations isn't available.

GitHub Issue Number: #
JIRA Issue-IX-4124

🆕 What is the new behavior?

Added a compatibility matrix

👨‍💻 Help & support

@netlify
Copy link
Copy Markdown

netlify Bot commented May 22, 2026

Deploy Preview for industrial-experience ready!

Name Link
🔨 Latest commit 645186e
🔍 Latest deploy log https://app.netlify.com/projects/industrial-experience/deploys/6a0fdf99c3abbf0008b50d12
😎 Deploy Preview https://deploy-preview-240--industrial-experience.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@1307-Dev 1307-Dev changed the title Added Compatibility matrix doc/update: Added Compatibility matrix May 22, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new compatibility matrix documentation page for version 5, detailing supported package versions, framework wrappers, and runtime requirements. It also updates the sidebar and the release version page to include links to this new resource. The review feedback highlights several violations of the project's style guide, specifically regarding the use of straight apostrophes instead of the required Unicode symbol, the use of passive voice, and incorrect capitalization of link text. Actionable suggestions were provided to align the documentation with the established grammar and formatting standards.

Comment thread docs/home/releases/compatibility-v5.md Outdated
Comment thread docs/home/releases/release-version.md Outdated
1307-Dev and others added 2 commits May 22, 2026 10:14
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Copy link
Copy Markdown
Collaborator

@danielleroux danielleroux May 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont see there any reliable way to keep this up to date without having outdated version. Other point I do not see there any point why this is necessary we have a package.json and npmjs as a registry which provides all necessary information already depending on the version.

If we update peerDependencies between lets say 5.1.0 to 5.2.0 we have always the latest peerDependencies listed here. For 5.1.0 users this information then is leading to a wrong information

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding the versioning, we could consider updating or adding a dedicated page for each sub-version per release. This would allow users to easily navigate between versions, for example, moving from 5.0.0 to 5.1.0, all within the same page.

As for the other point, I'll forward you the email chain where that discussion took place so you have all the context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants