Skip to content

chore(python): pin the backend to 1.11.1 - #400

Merged
vishnuv688 merged 1 commit into
mainfrom
chore/pin-backend-1.11.1
Sep 29, 2026
Merged

vishnuv688 merged 1 commit into
mainfrom
chore/pin-backend-1.11.1

Conversation

@github-actions

Copy link
Copy Markdown

@wdio/devtools-backend@1.11.1 is published, so the version a pip install user runs can move up from 1.11.0.

Opened by the npm release. scripts/check_backend_pin.py is 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.

@greptile-apps

greptile-apps Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 4/5

[Medium risk] Updates the pinned backend version for the Python package.

The PR appears safe to merge, though the pending pin fragments should be reconciled before the Python release.

Findings

  1. P2 Conflicting backend pin notes ▶

Summary

The PR pins the Python adapter’s npm backend to 1.11.1 and adds a patch-release fragment.

  • The pending 1.11.0 fragment should be reconciled so the next changelog identifies the backend version clearly.

Reviews (1) · Last reviewed commit: "chore(python): pin the backend to 1.11.1"

patch
---

Pin the backend a `pip install` user runs to 1.11.1.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Conflicting backend pin notes

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.

@vishnuv688
vishnuv688 merged commit 7bb3163 into main Sep 29, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants