Skip to content

ci: Release runs-on windows-latest (runner starvation potato) - #87

Merged
ScriptedAlchemy merged 1 commit into
mainfrom
cursor/release-windows-latest-potato-ed28
Sep 17, 2026
Merged

ScriptedAlchemy merged 1 commit into
mainfrom
cursor/release-windows-latest-potato-ed28

Conversation

@ScriptedAlchemy

Copy link
Copy Markdown
Owner

Summary

ubuntu-22.04 Release is still not assigned a runner after cancel and redispatch. Release run 35170786357 stays queued with runner_id 0 and an empty runner_name on label ubuntu-22.04.

This is an Actions capacity escape only. It flips the Release job runs-on from ubuntu-22.04 to windows-latest. It is not a Renovate 24.04 bump and it does not change Package CI or Changeset.

OIDC Release is unchanged: id-token: write, Changesets, and npm run release stay as they are. No local NPM_TOKEN.

shell: bash was already set on the pack smoke test and the npm version verify step. Single-line npm steps already ran on a prior windows-latest Release without a shell override, so this PR does not add more. Product code, package.json, and tests are untouched.

Do not merge from this agent.

Test plan

  • Diff is .github/workflows/release.yml runs-on only (ubuntu-22.04windows-latest)
  • ci.yml and changeset.yml are unchanged
  • Leave merge to the delivery whip; after merge, a new Release should request windows-latest instead of the starved ubuntu-22.04 queue
Open in Web Open in Cursor 

ubuntu-22.04 Release stays queued with runner_id 0. Flip only the
Release job label so OIDC publish can leave that pool. Steps unchanged.

Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
@changeset-bot

changeset-bot Bot commented Sep 17, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2ef168e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ScriptedAlchemy
ScriptedAlchemy marked this pull request as ready for review September 17, 2026 01:37
@ScriptedAlchemy
ScriptedAlchemy merged commit 59d6de8 into main Sep 17, 2026
1 of 2 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 17, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-17T01:40:59.265976Z 2ef168e Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2ef168e6aa

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

jobs:
release:
runs-on: ubuntu-22.04
runs-on: windows-latest

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Make the smoke-test paths Windows-aware

On windows-latest, the pack smoke-test will fail before the Changesets publish step: npm install --global --prefix "$install_root" places executable links directly in the prefix on Windows, while lines 56–58 invoke them from the Unix-only $install_root/bin directory. The npm folders documentation explicitly states that global executables are linked “directly into {prefix} on Windows.” Keep a Unix runner or select the Windows shim paths when running this job on Windows.

Useful? React with 👍 / 👎.

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