[chore] Use pseudo-versions to require extensiontest
#11677
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11677 +/- ##
=======================================
Coverage 91.64% 91.64%
=======================================
Files 442 442
Lines 23746 23746
=======================================
Hits 21761 21761
Misses 1616 1616
Partials 369 369 ☔ View full report in Codecov by Sentry. |
bogdandrutu
approved these changes
Nov 14, 2024
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.
Description
Now that the PR to split
extensiontestinto its own module (#11629) has landed, we can import the new module in an externally-resolvable way using the pseudo-version corresponding to the merge commit, similar to what I did forcomponenttest(#11668). After the next release (0.114.0), we will be able to use that version number instead for internal imports.