Skip to content

fix: W-23261603 pin CTC to Node 20 — unsettled await affects Node 22.23 too#455

Merged
setu4993 merged 1 commit into
salesforcecli:mainfrom
DylanZeigler:fix/ctc-node20-compat
Jul 1, 2026
Merged

fix: W-23261603 pin CTC to Node 20 — unsettled await affects Node 22.23 too#455
setu4993 merged 1 commit into
salesforcecli:mainfrom
DylanZeigler:fix/ctc-node20-compat

Conversation

@DylanZeigler

@DylanZeigler DylanZeigler commented Jul 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Pin nodeVersion: '20' in the publish workflow — lts/-1 (Node 22.23.0) also triggers the unsettled top-level await bug in @salesforce/change-case-management

@W-12345678@

Context

PR #454 pinned to lts/-1 but Node 22.23.0 backported the unsettled top-level await detection from Node 24, so CTC still fails. Node 20 is the last version that doesn't have this behavior.

Failing run (1.44.1 on Node 22.23.0): https://github.com/salesforcecli/plugin-agent/actions/runs/28488973503

Test plan

  • Re-run the 1.44.1 release via workflow_dispatch after merge and confirm CTC opens successfully
  • Remove this pin once @salesforce/change-case-management publishes a fix for the top-level await issue

Node 22.23.0 backported the unsettled top-level await detection from
Node 24, so lts/-1 still breaks @salesforce/change-case-management.
Pin to Node 20 until the CTC tooling is fixed.
@DylanZeigler DylanZeigler changed the title fix: pin CTC to Node 20 — unsettled await affects Node 22.23 too fix: W-23261603 pin CTC to Node 20 — unsettled await affects Node 22.23 too Jul 1, 2026
@setu4993 setu4993 merged commit e885d89 into salesforcecli:main Jul 1, 2026
4 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants