February 23

sfpowerscripts

February 23(v20.26.2) is all about quality of life improvements! We believe these enhancements will make your experience a bit more friendly.

⭐ New Features

• feat(validate): display info about the org that is used for validation #1239

Displays information about the org that is used for validation. Use --orginfo flag to display information to authenticate to the org that is being currently used by the validate job. If you are using -x flag, the information is valid only during the life of the current running job

• feat(validate): disable parallel testing using a flag #1255

Now you can disable parallel testing during validate across all packages using a new flag in --disableparalleltesting. Useful for scenarios when you are running full suite of tests across all the packages in a repo such as in nightly jobs and where do you need that additional consistency. This is also quite useful when you are recfactoring into writing better tests

• feat(validate): disable source package override in validate commands [#1240]

Use --disablesourcepkgoverride in validate to build and install unlocked packages in your project as such, instead of using source packages (metadata api) while validating your packages. This will give you more accurate behaviour especially when used on a sandbox. (validateAgainstOrg).

• feat(pool): recover orphaned scratch orgs #1234

sfpowerscripts will not utilize the description field of ScratchOrgInfo object to identify scratch orgs that are created. Using this information, the pool: delete command when coupled with --orphans flag can help you delete scratch orgs that were created but never got associated to any pools. The output is also prettified by classifying the operation

• feat(prepare): Add the ability to increment retry counts in prepare [#1233]

You can attempt more retries for packages installation in prepare by adding a maxRetryCount in your pool config. sfpowerscripts will now retry the package installation the number of times specified by this option. By default it always attempt for 2 installations during prepare

• feat(fetch) : Display error messages when fetching dev Scratch Org Pool in different git Repository for sfdx Project [#1251]
• feat(prepare): prevent from downloading / creating artifacts that are not used while preparing without installAll #1223

🪲 Bug Fixes

• fix(validate): fix for validate failing in individual mode due to missing dependencies #1241
• fix(apextests): fix apex tests trigger crashing on unlocked packages
• fix(fetch): sfpowerscripts:pool:fetch --json returns non-json #1254
• fix(external-dependencies): add support for detecting package ids with 15 chars and skipping it #1244
• fix(logs): add/remove misplaced spaces and typo (https://github.com/dxatscale/sfpowerscripts/actions/runs/4310619443/jobs/7519233163#step:4:37)
• fix(logs): add/remove misplaced spaces #1231
• fix(logs): fix typo on promote message in release/deploy

sfp-cli

We are reviving sfp-cli, as a unified cli for sfpowerscripts and other functionality to come. The repository is migrated to the sfpowerscripts repository and is operated as a project in the same mono repository space. The current version is still incredibly early in development, and we will be pushing in changes faster to stabilize.

⚠️ Warning
sfp-cli is still unstable and is recommended to be in use as a daily driver. Rest assured we are furiously working on it for making it prime time

❤️ Contributors

We'd like to thank all the contributors who worked on this release!

• @michallachowski
• @alanjaouen

January 23 - 4

sfpowercripts(v20.20.3) contains the following fixes

What's Changed

• Transitive Dependency Resolver doesn't resolve using higher version numbers of a package [#1221 ]
• Fix for crash in shrink command.[#1218 ] Thanks @jonathankretzmer

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/[email protected]...@dxatscale/[email protected]

January 23 - 3

sfpowerscripts(v20.20.1) is a patch release for the following issues

What's Changed

• Typo in log wording for post script by @nabondance in #1216
• sfpowerscripts:orchestrator:prepare fail when one scratchorg is allocated #1219

New Contributors

• @nabondance made their first contribution in #1216

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/[email protected]...@dxatscale/[email protected]

January 23 - 2

sfpowerscripts (v20.20.0) is a patch release with the following fixes

• fix(install): Fix Dependency install command not respecting user provided package keys
• fix(createunlocked): Display packages that are used while building and after building. This was a feature available in Nov 22 which got reverted.

We have noticed an issue with transitive dependency resolver, producing incorrect order of dependencies in some cases. If you notice such issue , please disable the transitive dependency resolver temporarily using the example as below

 "plugins": {   
     "sfpowerscripts": {         
       "disableTransitiveDependencyResolver":true,
       }
 }

We are actively working on resolving the issue asap

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/[email protected]...@dxatscale/[email protected]

January 23 - 1

sfpowerscripts (v20.19.8) is a patch for the following issues

What's Changed

• fix(expand): fix expand crashing if user defined external dependency map is not provided
• fix(log): Typo in log wording for post script by @nabondance in #1216

New Contributors

• @nabondance made their first contribution in #1216

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/[email protected]...@dxatscale/[email protected]

January 23

First release of 2023 is out (v20.19.6) and is packed with goodies. Read about the new features/enhancements and bug fixes. We hope it improves your dx@scale experience significantly.

⭐ New Features

• sfpowerscripts now support for declarative field history tracking and feed tracking. Read more on how to use this feature here @MengAQi has written a blog which details more on how this functionality work under the hoods. Check out the article here
• Missed declaring a package dependency? sfpowerscripts now feature a transitive dependency resolution which fills in the gaps. Don't like it, use disableTransitiveDependencyResolver:false to turn this feature off. Read more about the feature here

  "plugins": {
          "sfpowerscripts": {
              "disableTransitiveDependencyResolver": true
          }
  

• 3 New additional commands to help with dependency management, with more enhancements slated for upcoming releases. These commands are in the dependency topic

Commmand	Description
dependency: expand	Expand the dependency list in sfdx-project.json file for each package, fix the gap of dependencies from its dependent packages
dependency: shrink	Shrink the dependency list in sfdx-project.json file for each package, remove duplicate dependencies that already exist in its dependent packages
dependency: install	Install all the external dependencies of a given project

⭐ Enhancements

• Add support for sfpowerscripts orchestrator extensions to unlocked packages #1204
• Additional parameters to pre/post script to manipulate contents of a package #1196
• publish command to push only packages version tags #1183
• Create scratch orgs in parallel during prepare #1142
• More concise logs, by removing borders around tables

🪲 Bug Fixes

• pool. Available metrics not reporting poolname #1214
• Unpackaged metadata not provided to sfdx build in newest sfpowerscripts version #1202
• GitLab NPM Scope adds second @ in orchestrator:release #1200
• releasedefinition:generate does not generate "promotePackagesBeforeDeploymentToOrg" attributes correctly to Release Definition File #1180
• Quickbuild command is not respecting .forceIgnore specific file #1178
• Publish command tags HEAD instead of artifact commit ID #983

New Contributors

• @gz77a made their first contribution in #1181

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/[email protected]...@dxatscale/[email protected]

November 22 - 4

sfpowerscripts (v20.2.11) fixes the following issue

• Build failure reasons not reported since update #1177 Thanks @con242

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/[email protected]...@dxatscale/[email protected]

November 22 - 3

sfpowerscripts (v20.2.10) fixes the following issues

• fix for sfpowerscripts:orchestrator:quickbuild not honoring config path #1176 Thanks @yippie
• validateAgainstOrg not installing external dependencies in individual mode
• fix typos and double spaces in log messages (#1171) Thanks @attilah

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/[email protected]...@dxatscale/[email protected]

November 22 - 2

sfpowerscripts ( v20.2.6 ) is a hotfix for the following issue

• GitLab NPM Scope failures in Orchestration Jobs for Latest November 22-1 Release #1168

November 22 - 1

v20.2.5 is hotfix for

• Update core libs to fix 'org not found' issues during lengthy deployments