ci: repair scheduled drift guards (apidocs pnpm, coreutils push)#2159
Merged
Conversation
Both weekly drift workflows failed on main: - apidocs-drift typescript job: pnpm/action-setup@v6 no longer defaults a version and there is no root package.json for it to read packageManager from, so setup errored before any drift check. Pin version: 10.33.0 to match js.yml / publish-js.yml. - coreutils-args-drift open-pr job: git push --force-with-lease aborted with "stale info" because the drift branch already existed remotely but the fresh main checkout has no remote-tracking ref to lease against. Use plain --force on this automation-owned, fully-regenerated branch.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | 180fd50 | Commit Preview URL Branch Preview URL |
Jul 13 2026, 09:16 AM |
This was referenced Jul 13, 2026
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
1 participant
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.
What changed
Fixes two weekly scheduled drift-guard workflows that have been failing on
main, so both go green again and resume doing their job (detecting API/upstream drift).typescriptjob now pinspnpmversion: 10.33.0in itsSetup pnpmstep, matchingjs.yml/publish-js.yml.open-prjob now pushes the automation branch with plain--forceinstead of--force-with-lease.Why
Both guards were red on 2026-07-13 (Monday schedule):
typescriptjob died at Setup pnpm withError: No pnpm version is specified.pnpm/action-setup@v6no longer ships a default version; it readspackageManagerfrom the rootpackage.json, which this repo doesn't have (the field lives incrates/bashkit-js/package.json). Every other workflow already pinsversion: 10.33.0; this one was the sole exception, so it never reached the actual drift check.open-prjob failed atgit push:--force-with-leaseneeds a remote-tracking ref to lease against. The freshmaincheckout has none for the drift branch, so once the branch exists from a prior week's run the lease check aborts with stale info. The branch is owned exclusively by this automation and fully regenerated each run, so plain--forceis correct here.Before / After
apidocs-drift→Error: No pnpm version is specifiedbefore any drift check;coreutils-args-drift→failed to push some refs ... (stale info)after successfully regenerating.apidocs-drifttypescriptreaches the regenerate/diff step;coreutils-args-driftopen-prpushes and opens/updates the drift PR. Both runs conclude successfully.Risk
Checklist