Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@salesforce/plugin-community 3.0.2 update causes sf community publish commands to fail with "JitPluginInstallError: Could not install @salesforce/plugin-community " #2595

Closed
Ryanckhou opened this issue Dec 5, 2023 · 2 comments
Labels
more information required Issue requires more information or a response from the customer

Comments

@Ryanckhou
Copy link

Summary

We are getting an error whenever we are trying to publish an SF community. This started on November 29th, 1:32PM CST. We have the same pipelines working with the most recent success at November 29th, 10:26AM CST

Our Azure DevOps pipelines are failing to pushing to the community. Looks like there was an update on the @salesforce/plugin-community from
[email protected] to [email protected] We have the same pipelines working at

Steps To Reproduce

  • Connect CLI to org with experience cloud site setup
  • Set up project
  • execute "sf community publish --name -o "

Expected result

123

Actual result

========================== Starting Command Output ===========================
/usr/bin/bash /home/vsts/work/_temp/15c8537c-8fe4-4f5d-913b-13782e5e86ab.sh
Installing plugin [email protected]... yarn add v1.22.19
Installing plugin [email protected]... [1/4] Resolving packages...Installing plugin [email protected]... [2/4] Fetching packages...Installing plugin [email protected]... info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.Installing plugin [email protected]... failed
JitPluginInstallError: Could not install @salesforce/plugin-community
Code: JitPluginInstallError
##[error]Bash exited with code '1'.

System Information

using git bash
{
"cliVersion": "@salesforce/cli/1.86.7-legacy.0",
"architecture": "win32-x64",
"nodeVersion": "node-v18.15.0",
"osVersion": "Windows_NT 10.0.19045",
"shell": "cmd.exe",
"rootPath": "C:\Program Files\sfdx\client\sf",
"pluginVersions": [
"@oclif/plugin-autocomplete 2.3.1 (core)",
"@oclif/plugin-commands 2.2.17 (core)",
"@oclif/plugin-help 5.2.11 (core)",
"@oclif/plugin-not-found 2.3.26 (core)",
"@oclif/plugin-plugins 3.1.6 (core)",
"@oclif/plugin-search 0.0.18 (core)",
"@oclif/plugin-update 3.1.22 (core)",
"@oclif/plugin-version 1.3.6 (core)",
"@oclif/plugin-warn-if-update-available 2.0.41 (core)",
"@oclif/plugin-which 2.2.22 (core)",
"@salesforce/cli 1.86.7-legacy.0 (core)",
"apex 2.3.4 (core)",
"auth 2.8.4 (core)",
"data 2.4.5 (core)",
"deploy-retrieve 1.13.5 (core)",
"info 2.6.30 (core)",
"limits 2.3.23 (core)",
"login 1.2.15 (core)",
"org 2.9.19 (core)",
"schema 2.3.17 (core)",
"settings 1.4.17 (core)",
"sobject 0.1.32 (core)",
"source 2.10.22 (core)",
"telemetry 2.2.1 (core)",
"templates 55.5.2 (core)",
"trust 2.4.27 (core)",
"user 2.3.20 (core)"
]
}

@Ryanckhou Ryanckhou added the investigating We're actively investigating this issue label Dec 5, 2023
Copy link

github-actions bot commented Dec 5, 2023

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.

Copy link

github-actions bot commented Dec 5, 2023

Hello @Ryanckhou 👋

It looks like you're using an outdated version of Salesforce CLI. sf (v1) is in "maintenance mode" as of July 12, 2023. We highly recommend you move from sf (v1) to sf (v2) ASAP.

Moving to sf (v2) is easy and takes just two commands. Find all the information here.

After you move to the latest version of sf (v2), run your command again and provide the output of sf version --verbose --json.

@github-actions github-actions bot added more information required Issue requires more information or a response from the customer and removed investigating We're actively investigating this issue labels Dec 5, 2023
@Ryanckhou Ryanckhou closed this as not planned Won't fix, can't repro, duplicate, stale Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more information required Issue requires more information or a response from the customer
Projects
None yet
Development

No branches or pull requests

1 participant