chore(python): pin the backend to 1.11.1 - #400
Merged
Merged
Conversation
|
| patch | ||
| --- | ||
|
|
||
| Pin the backend a `pip install` user runs to 1.11.1. |
There was a problem hiding this comment.
The next Python release will include this note alongside the still-pending note saying pip install users run backend 1.11.0. The changelog will then claim both 1.11.0 and 1.11.1 for the same release, making the shipped version unclear. Please reconcile the older note before release.
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.
@wdio/devtools-backend@1.11.1is published, so the version apip installuser runs can move up from 1.11.0.Opened by the npm release.
scripts/check_backend_pin.pyis what decides whether this pin is serviceable — it asks the published tarball whether it carries every contract name the adapter needs, so let that check run before merging.If this PR shows no checks, it was raised with
GITHUB_TOKEN, which GitHub will not let start a workflow. Close and reopen it, or push an empty commit, to get CI.