Skip to content

fix(ci): widen resolve-dev-version search window for quiet main#658

Open
jhamon wants to merge 1 commit intomainfrom
ci/widen-resolve-dev-version-window
Open

fix(ci): widen resolve-dev-version search window for quiet main#658
jhamon wants to merge 1 commit intomainfrom
ci/widen-resolve-dev-version-window

Conversation

@jhamon
Copy link
Copy Markdown
Collaborator

@jhamon jhamon commented May 8, 2026

Summary

  • Increases --limit from 10 to 100 in the resolve-dev-version job's gh run list call
  • At hourly cadence, 100 candidates covers ~4 days of quiet main (no new commits → check-changes skip → success without artifact)
  • Fixes false-positive CI failures when main is quiet for >~10 hours

Root cause

resolve-dev-version listed only the 10 most recent successful Dev Build & Publish runs. When main has had no new commits for >10 hours, all recent runs are no-op skips (check-changes gate completes as success without uploading a dev-version artifact). The resolver exhausted its 10-candidate window and errored as if the dev pipeline was broken. (CI-0061)

Verification

Release Readiness run on this branch with skip_integration=true:
https://github.com/pinecone-io/python-sdk/actions/runs/25576424039

Resolve latest dev wheel version job completed successfully. All wheel build jobs green.


Note

Low Risk
Low risk: only adjusts GitHub Actions workflow logic to scan more past successful runs, reducing false CI failures without touching product code.

Overview
Improves release-readiness robustness when main is quiet. The resolve-dev-version step now searches a larger set of recent successful dev-publish runs (limit 10 → 100) when looking for the dev-version artifact, and documents the rationale.

This prevents the workflow from failing when recent successful runs were no-op skips that didn’t upload the artifact.

Reviewed by Cursor Bugbot for commit 41c5c44. Bugbot is set up for automated code reviews on this repo. Configure here.

Increase --limit from 10 to 100 when listing recent successful Dev Build &
Publish runs. At hourly cadence, 100 candidates covers ~4 days of quiet main
(no new commits triggers check-changes skip, producing success without a
dev-version artifact). Previously, >~10 skipped runs could exhaust the window
and false-positive as a broken dev pipeline.
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.

1 participant