Relax reverse_markdown dependency to Support v3
#729
Merged
Conversation
This file contains 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
The `reverse_markdown` library has been updated to version 3. The only breaking change in this version is the removal of support for Ruby versions <= 2.6. This commit relaxes the dependency to allow versions up to `< 4`, ensuring compatibility with the latest `reverse_markdown` while maintaining support for Ruby 2.6. Closes castwide#728 Note: The CI failure is unrelated to this change and is being tracked in issue castwide#726.
|
👍 |
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.
The
reverse_markdownlibrary has been updated to version 3. The only breaking change in this version is the removal of support for Ruby versions <= 2.6.This commit relaxes the dependency to allow versions up to
< 4, ensuring compatibility with the latestreverse_markdownwhile maintaining support for Ruby 2.6.Closes #728
Note: The CI failure is unrelated to this change and is being tracked in issue #726.