Remove downstream CI checks#286
Open
asnare wants to merge 3 commits into
Open
Conversation
asnare
added
internal
github_actions
|
✅ 40/40 passed, 6 skipped, 6m51s total Running from acceptance #283 |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
We can't reliably test downstream compatibility at the moment; instead packages should express upper bounds and opt-in to new releases.
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
2 participants
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.
Changes
The downstream checks were disabled when we migrated from Hatch, and this PR removes them entirely: due to compatibility issues with transitive issues we've needed to specify explicit upper bounds on dependencies. With this in place downstream projects need to opt-in to new releases.
Linked issues
Follows #235.