Skip to content

[BUG]: 2.155.7 release notes list the fix for #3664, but 2.155.7 pins @salesforce/packaging 5.0.20 without it #3671

Closed

Description

@Z-kondokazuhiro

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

#3664

Command

sf package uninstall --wait / sf package uninstall report (affected by #3664; I checked the installed files of an npm global install and did not run these commands against an org)

Org Type

Not applicable

Did this work before?

No, this is a new bug

Last Working Version

No response

Summary

Thank you for fixing #3664. This report is only about which release delivers the fix.

The release notes list the fix under 2.155.7 (October 21, 2026) [stable]:

FIX: sf package uninstall --wait and sf package uninstall report now show the actual uninstall failure details instead of a MALFORMED_QUERY error.

However, the 2.155.7 npm package does not include this fix:

Timeline (UTC):

So the 2.155.7 npm package could not include the fix. With npm, 2.155.7 (the stable release as of October 24, 2026) still installs @salesforce/packaging 5.0.20, which has the old code, while the notes say it is fixed.

Repository to Reproduce

No repository is needed. The check needs no org and no project.

Steps to reproduce

With @salesforce/cli 2.155.7 installed globally with npm, run:

$ sf --version
@salesforce/cli/2.155.7 darwin-arm64 node-v22.18.0

$ npm ls -g @salesforce/packaging
~/.nvm/versions/node/v22.18.0/lib
└─┬ @salesforce/cli@2.155.7
  └─┬ @salesforce/plugin-packaging@3.0.14
    └── @salesforce/packaging@5.0.20


$ grep -n "PackageVersionUninstallRequestError" "$(npm root -g)/@salesforce/cli/node_modules/@salesforce/packaging/lib/package/packageUninstall.js"
33:    const errorQueryResult = await conn.tooling.query(`"SELECT Message FROM PackageVersionUninstallRequestError WHERE ParentRequest.Id = '${id}' ORDER BY Message"`);

Expected Result

The release notes list the fix under 2.155.7. So I expected 2.155.7 to install @salesforce/packaging 5.0.21 or later. In 5.0.21, line 33 of lib/package/packageUninstall.js has no extra double quotes around the query:

const errorQueryResult = await conn.tooling.query(`SELECT Message FROM PackageVersionUninstallRequestError WHERE ParentRequest.Id = '${id}' ORDER BY Message`);

If 2.155.7 cannot include the fix, I expected the release notes to list it under the release that includes it.

Actual Result

2.155.7 installs @salesforce/packaging 5.0.20. Line 33 of the installed packageUninstall.js still wraps the query in double quotes (see the output above). forcedotcom/packaging#945 removes these quotes.

Error Message

System Information

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.155.7",
  "nodeVersion": "node-v22.18.0",
  "osVersion": "Darwin 27.0.0",
  "rootPath": "~/.nvm/versions/node/v22.18.0/lib/node_modules/@salesforce/cli",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 4.0.4 (core)",
    "@oclif/plugin-commands 5.0.4 (core)",
    "@oclif/plugin-help 7.0.4 (core)",
    "@oclif/plugin-not-found 4.0.4 (core)",
    "@oclif/plugin-plugins 7.0.7 (core)",
    "@oclif/plugin-search 2.0.0 (core)",
    "@oclif/plugin-update 5.0.4 (core)",
    "@oclif/plugin-version 3.0.5 (core)",
    "@oclif/plugin-warn-if-update-available 4.0.3 (core)",
    "@oclif/plugin-which 4.0.4 (core)",
    "@salesforce/analytics 1.4.85 (user) published 14 days ago (Sat Oct 10 2026)",
    "@salesforce/cli 2.155.7 (core)",
    "agent 2.2.2 (core)",
    "apex 4.4.3 (core)",
    "api 2.0.17 (core)",
    "auth 5.0.16 (core)",
    "community 4.0.13 (user) published 13 days ago (Sat Oct 10 2026) (latest is 4.0.14)",
    "data 5.1.16 (core)",
    "deploy-retrieve 4.2.14 (core)",
    "info 4.0.16 (core)",
    "limits 4.0.6 (core)",
    "marketplace 2.0.17 (core)",
    "org 6.0.26 (core)",
    "packaging 3.0.14 (core)",
    "schema 4.0.12 (core)",
    "settings 3.0.14 (core)",
    "sobject 2.0.12 (core)",
    "telemetry 4.2.0 (core)",
    "templates 57.4.6 (core)",
    "trust 4.0.20 (core)",
    "user 5.0.11 (core)"
  ]
}

Additional Information

Earlier releases with the same pattern. For each release below, I checked the npm-shrinkwrap.json in its published npm package. For the source-deploy-retrieve and source-tracking rows, I also compared the code of the pinned version with a fixed version. The only runtime change in salesforcecli/plugin-org#1775 is the open version range, so for that row I compared versions only.

Release notes section FIX entry Pinned in that release Next listed release that pins a fixed version
2.152.14 (September 30, 2026) sf org open (#3646, salesforcecli/plugin-org#1775; the PR raises open to ^11.0.3) plugin-org 6.0.13, open 11.0.1 2.153.5 (plugin-org 6.0.17, open 11.0.4)
2.151.7 (Sept 23, 2026) AiAgentDefinitionVersion (forcedotcom/source-deploy-retrieve#1826) source-deploy-retrieve 13.3.0 2.152.14 (13.4.0)
2.150.6 (Sept 2, 2026) ENOTDIR with lwc/README.md (#3627, forcedotcom/source-deploy-retrieve#1823) source-deploy-retrieve 13.1.1 2.151.7 (13.3.0)
2.150.6 (Sept 2, 2026) Decomposed permission set (#3621, forcedotcom/source-deploy-retrieve#1817) source-deploy-retrieve 13.1.1 2.151.7 (13.3.0)
2.146.3 (August 5, 2026) Source tracking after deploying platform events and similar types (#3512, forcedotcom/source-tracking#868) source-tracking 7.8.19 2.147.7 (8.0.0)

The essence. In each of these cases, as in 2.155.7, the FIX is listed under a release whose npm-shrinkwrap.json pins a dependency version without the fix. In the earlier cases, the fix reached npm users in the next listed release, and that release's notes do not mention it.

About 2.156.x. The current release candidate, 2.156.7, no longer ships npm-shrinkwrap.json. A lockfile-only resolution of it on October 24 picked @salesforce/packaging 5.0.26, which includes this fix.

Requests:

  1. Could you please confirm this? If it is confirmed, could you move this entry from 2.155.7 to the first release that includes @salesforce/packaging 5.0.21 or later (2.156.7, as far as I can tell)? (In that entry, the PR link points to salesforcecli/packaging, which returns 404; the PR is fix: remove literal quotes from SOQL in getUninstallErrors-W-24463742 packaging#945.)
  2. As a gentle suggestion: it would help users if each FIX were listed under the first release that includes it.

Thank you very much for your work on Salesforce CLI.

Screenshots or Log Files

No response

Activity

  1. github-actions commented on Oct 24, 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. jfeingold35 commented on Oct 26, 2026

    @jfeingold35

    @Z-kondokazuhiro , it looks like what happened is that the Dependabot PR for @salesforce/plugin-packaging that would have updated the dependency on @salesforce/packaging failed. I'm looking into that now. Once we get it merged, everything should sort itself out.

  3. jfeingold35 commented on Oct 26, 2026

    @jfeingold35

    @Z-kondokazuhiro , the Dependabot PR has been merged, so this should sort itself out in tomorrow's release. I'm going to close this for now.

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