Merged
Conversation
v2.20 added supports for cascading deletes
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
Acceptheadernodetotarget(deprecated in v2.8)test.osf.ioBackground
The recent Accept header fix (#163) corrected the header name from
Accept-Headerto
Accept, but left version pinning disabled (version = NULL) for safety. Withouta pinned version, the OSF API defaults all requests to v2.0, which is what the package
has always been using.
Pinning to the most recent OSF API version will ensure consistent/predictable API behavior and prevent the package
from breaking if OSF makes breaking changes in the future.