Repository navigation
chore: require parsanol >= 1.3.61 (PARG) - #791
Merged
Merged
Conversation
The ISC runtime parses through the shipped .parg artifact and falls back to the DSL grammar when Parsanol::PARG is absent. The owner chose to force the floor instead: 1.3.61 is the first release carrying PARG. The DSL fallback stays as a safety net for install-time edge cases.
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.
Owner decision per the #790 note: force the parsanol floor instead of relying on the DSL fallback. 1.3.61 is the first release carrying
Parsanol::PARG(the artifact runtime from #790). The constraint keeps the previous breadth (< 2) while requiring PARG; the DSL-grammar fallback remains as a safety net.