Add version compatibility to README - #28
Merged
Merged
Conversation
URJala
approved these changes
Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add more information about version compatibility to README.
Note
Low Risk
Documentation-only README change with no code or deployment behavior impact.
Overview
Adds a Version compatibility subsection under Install on a robot with a matrix of PolyScope X (10.7–10.14) versus URCapX releases 0.1.0, 1.0.0, and 1.1.0, using ✅, ✗, and ? markers.
A note calls out that 10.14 with 1.0.0/1.1.0 (✅*) can look valid on the pendant while remote program code cannot be fetched, so the program will not run.
Reviewed by Cursor Bugbot for commit 0712df7. Bugbot is set up for automated code reviews on this repo. Configure here.