Repository navigation
Align Runestone pin with protected ranges and active sessions - #37
Merged
Merged
Conversation
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
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.
Update both exact Runestone pins to the merged revision a10c06ab0e9823cc9ede0bc8a33310cb4cf0e121 from simonbs/Runestone#455. The app's protected-range integration needs the same revision; changing only its direct dependency would conflict with this package's exact requirement.
No grammar sources or products change. The merged framework tree is identical to the tested head. Validated through https://github.com/simonbs/RunestoneEditor/pull/47: the published graph resolved with the canonical lock, and all 21 focused app integration tests and 3 Markdown protection tests passed before repinning to the equivalent merged framework commit.