Skip to content

🐛 fix(workflows): name maintenance patches apart - #51

Merged
gaborbernat merged 1 commit into
mainfrom
fix/unique-maintenance-artifact
Nov 4, 2026
Merged

gaborbernat merged 1 commit into
mainfrom
fix/unique-maintenance-artifact

Conversation

@gaborbernat

Copy link
Copy Markdown
Member

A caller that runs update-python-dependencies and upgrade-release-tools in the same workflow run fails in open-maintenance-pr with None of the provided artifact IDs were found (simplint run). Both reusables uploaded an artifact named maintenance-patch, and the runtime artifact list that download-artifact searches keeps only the newest artifact per name, so the other job's ID is never found. A rerun fails the same way.

Each reusable now uploads under its own name: maintenance-patch-python-dependencies and maintenance-patch-release-tools. open-maintenance-pr downloads by ID, so callers need no change.

simplint's update_dependencies calls update-python-dependencies and
upgrade-release-tools in one run. Both uploaded a `maintenance-patch`
artifact, and the runtime artifact list keeps only the newest artifact
per name, so the older ID failed with `None of the provided artifact IDs
were found`. Each reusable now uploads under its own name; the download
side already selects by ID and needs no change.
@gaborbernat
gaborbernat merged commit 2627ba5 into main Nov 4, 2026
10 checks passed
@gaborbernat
gaborbernat deleted the fix/unique-maintenance-artifact branch November 4, 2026 21:46
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