Document the current substrate plugin as the 0.21.x install target - #32
Merged
Conversation
Signed-off-by: Pavel-Tk <110731619+Pavel-Tk@users.noreply.github.com>
Pavel-Tk
force-pushed
the
docs-current-plugin-target
branch
from
September 3, 2026 18:44
c388fae to
e2cc9fc
Compare
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
1 participant
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.
Summary
An installing agent reading COMPATIBILITY.md, SECURITY.md, CHANGELOG.md, or the legacy
src/substrate_wiki README concluded the repository certifies only Hermes 0.20.x and blocked
a 0.21.0 install. This makes the current plugins/substrate (0.2.x, Hermes 0.21.x) the
documented current install target in every doc an agent may consult, and labels legacy
substrate_wiki content explicitly.
Changed
Validation