chore(release): open the Python backend pin bump automatically

[vishnuv688]

What & why

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Polish (an improvement to an existing feature)
• Breaking change (existing behavior changes for users)
• Documentation
• Internal (build, CI, dependencies, tooling)

Packages touched

• shared (types and contracts)
• core (framework-agnostic capture/reporting)
• elements (published element/snapshot API — @wdio/elements)
• service (WebdriverIO adapter)
• nightwatch-devtools (Nightwatch adapter)
• selenium-devtools (Selenium adapter)
• selenium-devtools-py (Selenium Python adapter)
• backend (server)
• app (UI)
• script (page-injected runtime)
• trace (Trace mode)

Notes for reviewers

Screenshots / recordings

[greptile-apps]

Confidence Score: 5/5

[High risk] Release workflow now opens pull requests with elevated permissions.

The PR appears safe to merge; no new actionable issue or outstanding previous finding remains.

Summary

The npm release workflow now opens a Python backend pin-bump PR after publication. The latest revision adds a forward-only version check and continues an existing PR branch without force-pushing it.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Publish backend] --> B{Latest release and newer than pin?}
  B -- No --> C[Leave pin unchanged]
  B -- Yes --> D[Continue existing branch or create one]
  D --> E[Stage pin and fragment]
  E --> F[Push without force if changed]
  F --> G[Reuse open PR or create PR]

Loading

_{Reviews (3) · Last reviewed commit: "fix(release): never force the pin branch..."}