question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Announcement: Rollback of 50.13.3 CLI 7.84.2

See original GitHub issue

We had to roll back yesterday’s CLI release because it caused multiple issues for customers. In the spirit of transparency, we want to explain what happened and how we plan to fix it.

As many of you know, we’ve made great progress in open sourcing the CLI (https://developer.salesforce.com/blogs/2020/05/open-sourcing-salesforce-cli.html); stay tuned for a blog post updating the community soon. We’re committed to transitioning the CLI to be fully open-sourced. However, the transition involves moving many commands and builds to multiple public repositories and environments. We are also currently releasing the CLI using both the old and new system.

We haven’t released a new version of the CLI in over a month because of Dreamforce and the holidays. This delay created a release with a lot of changes (https://github.com/forcedotcom/cli/tree/main/releasenotes#50133-january-14-2021---cli-7842). Nonetheless, the release candidate sat in `latest-rc’ for over a week to allow for testing, and everything seemed to work correctly in our CI and testing environments.

However, when the CLI was promoted Thursday, January 14, 2021, the archives and plug-in versions were pointing to incorrect and incompatible dependency versions, which caused a variety of regressions. We are still investigating what exactly happened and why our tests didn’t catch the issues. We’re working to ensure that the new build system will prevent these regressions from happening in the future.

We plan to fix all the dependency issues and build a new latest-rc version next week, and then promote it on Thursday, January 28, 2021.

We apologize for the inconvenience.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:17
  • Comments:14

github_iconTop GitHub Comments

3reactions
amphrocommented, Jan 21, 2021

The stable channel, which sfdx update points to, seems to be on different versions… I can look into that a little more.

3reactions
davisaglicommented, Jan 20, 2021

@amphro Could you clarify what it means that the 50.13.3 release was rolled back? I ran sfdx update this morning, and ended up with version 50.13.3 of the salesforcedx plugin. I had seen this announcement and it took me quite some time to realize that I have the wrong version, since I was expecting that sfdx update would not install a release that was rolled back.

And to echo the previous comment – now that I have the wrong release, how do I install the previous one?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Daniel Ballinger on Twitter: "My SFDX CLI was broken by the 7.84.2 ...
We had to roll back yesterday's CLI release because it caused multiple issues for customers. In the spirit of transparency, we want to...
Read more >
cli windows Drive Path Casing Issue - GitAnswer
I'm seeing the file path's casing change based on how the cli gets spawned e.g. ... cli announcement: Rollback of 50.13.3 CLI 7.84.2...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found