Skip to content

[BUG]: Bump @oclif/core from 4.14.0 -> 5.1.0 to resolve issue using --sfdx-url-stdin #3657

Closed

Description

@ns-091

Before You Submit

  • I'm using the latest version of Salesforce CLI
  • I've searched the existing issues
  • I've run sf doctor to diagnose common issues

Related Issue

#3647

Command

sf org login sfdx-url --sfdx-url-stdin

Org Type

Production

Did this work before?

No, this is a new bug

Last Working Version

No response

Summary

Issue originally reported in #3647 was due to issue with 3rd party package.

Issue has been fixed in https://github.com/oclif/core/releases/tag/5.1.0 that was causing sf org login sfdx-url --sfdx-url-stdin to intermittently fail in CI pipelines.

Repository to Reproduce

No response

Steps to reproduce

  1. Run sf org login sfdx-url --sfdx-url-stdin in CI pipeline
  2. Will intermittently fail due to hardcoded 10ms delay in @oclif/core

Expected Result

Should consistently read the sfdx-url from std without failing.

Actual Result

Intermittently fails as timeout reached before input is read

System Information

{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.151.7",
  "nodeVersion": "node-v22.23.2",
  "osVersion": "Windows_NT 10.0.26200",
  "shell": "powershell",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 4.0.0 (core)",
    "@oclif/plugin-commands 5.0.0 (core)",
    "@oclif/plugin-help 7.0.0 (core)",
    "@oclif/plugin-not-found 4.0.0 (core)",
    "@oclif/plugin-plugins 6.0.0 (core)",
    "@oclif/plugin-search 2.0.0 (core)",
    "@oclif/plugin-update 5.0.0 (core)",
    "@oclif/plugin-version 3.0.0 (core)",
    "@oclif/plugin-warn-if-update-available 4.0.0 (core)",
    "@oclif/plugin-which 4.0.0 (core)",
    "@salesforce/cli 2.151.7 (core)",
    "agent 2.0.5 (core)",
    "apex 4.1.1 (core)",
    "api 2.0.9 (core)",
    "auth 5.0.6 (core)",
    "code-analyzer 5.15.0 (user) published 62 days ago (Wed Jul 29 2026) (latest is 5.16.0)",
    "data 5.1.7 (core)",
    "deploy-retrieve 4.2.0 (core)",
    "info 4.0.9 (core)",
    "limits 4.0.4 (core)",
    "marketplace 2.0.5 (core)",
    "org 6.0.11 (core)",
    "packaging 3.0.6 (core)",
    "schema 4.0.6 (core)",
    "settings 3.0.6 (core)",
    "sobject 2.0.5 (core)",
    "telemetry 4.0.6 (core)",
    "templates 57.1.0 (core)",
    "trust 4.0.10 (core)",
    "user 5.0.2 (core)"
  ]
}

Additional Information

Only breaking changes from version 4 -> 5

drop EOL Node versions
require Node >=22, drop EOL Node version

Screenshots or Log Files

No response

Activity

  1. github-actions commented on Sep 30, 2026

    @github-actions

    Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

  2. WillieRuemmele commented on Sep 30, 2026

    @WillieRuemmele
    Member

    The fix is already on its way through the release pipeline:

    Once you're on a CLI version that includes @oclif/core@5.1.0+, you can set OCLIF_STDIN_TIMEOUT_MS to a higher value (e.g. 1000) in your CI environment to control the stdin read timeout. This env var is not available in the current latest (2.151.7, which ships @oclif/core@5.0.0), so you'd need to install the nightly (npm install @salesforce/cli@nightly) or wait for the Oct 8 latest release to use it.

    Note: the issue title says "from 4.14.0" but the CLI is already on @oclif/core@5.x. The 4.14.0 you may be seeing is a transitive dependency from plugins that still reference @oclif/core@^4.

  3. iowillhoit commented on Oct 12, 2026

    @iowillhoit
    Contributor

    Hey all, the latest version of the CLI is currently using @oclif/core version 5.1.2. Closing this issue

    Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    investigatingWe're actively investigating this issuevalidatedVersion information for this issue has been validated

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions