forcedotcom / code-builder-feedback

This repository is used to collect feedback for the Code Builder beta.
29 stars 2 forks source link

Issues with SFDX CLI not up to date #211

Closed FabienTaillon closed 1 year ago

FabienTaillon commented 1 year ago

I'm using local VS Code on a computer, and get a warning that flags need to be replaced in one command:

VS Code

I change them in my scripts, push to GitHub. Later on, on another computer where I don't have everything installed I use Code Builder, but then the updated script doesn't work:

Code Builder

This Code Builder env has been created this week, so it's not an old one, but still it has an old CLI version, 2 months according to the CLI release date: https://www.npmjs.com/package/sfdx-cli?activeTab=versions

So there are 2 problems to me:

git2gus[bot] commented 1 year ago

This issue has been linked to a new work item: W-12528977

jonnyhork commented 1 year ago

@FabienTaillon Thanks for creating this issue. We recently updated the image behind Code Builder, which includes the latest version of the CLI at the time of its release. If you start any of your Code Builder instances and check the CLI version with sfdx --version we should expect to see sfdx-cli/7.188.1 linux-x64 node-v18.12.0. Please let me know you still see an older version.

Not being able to sfdx update prevent us from solving this

The best way to update the version of the CLI in Code Builder is to use npm with npm install -g sfdx-cli

FabienTaillon commented 1 year ago

Thanks. I think the SalesforceDX docker image is updated every week like the CLI, could be good at some point to have the same release update for CodeBuilder image. I'll use the npm way to update in the meantime, thanks 👍

jonnyhork commented 1 year ago

Sounds good, we definitely have plans to improve how we manage the Code Builder image so that there are regular, mostly automated updates similar to the SFDX docker image. Thanks for your patience on this.

Ironically, since I told you we updated the Code Builder image yesterday, we discovered a regression and had to roll back to an earlier version. We are working on a fix, but I think you should be ok with npm for now.