Keeping HookTest below v2.0 for compatibility.#18
Merged
pharos-alexandria merged 1 commit intoJun 18, 2026
Conversation
I am proposing this change to pin HookTest to <2.0 to ensure your repository remains functional. The upcoming HookTest v2.0 (scheduled for release the week of June 22nd) only supports CiteStructure approaches, which would break your current setup. By pinning the version now, you can maintain stability.
524eb97
into
PatristicTextArchive:public
1 of 2 checks passed
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.
I am proposing this change to pin HookTest to <2.0 to ensure your repository remains functional. The upcoming HookTest v2.0 (scheduled for release the week of June 22nd) only supports CiteStructure approaches, which would break your current setup. By pinning the version now, you can maintain stability.