May 22

sfpowerscripts(v13.6.16) features the following

⭐ New Features

• Introducing fast feedback mode, Now run your validation checks more faster by selectively deploying only the changed components of the package and triggering only the impacted test class. Read the decision record here. You can turn on fast feedback by adding the --fastfeedback flag in the validate command. We believe this change along with upcoming changes in 'prepare' will ensure the validation experience remains performant.

-We would like to thank @nawforce for his amazing work on apex-link and apex-parser whic powers our apex related workflows.

⭐ Enhancements

• Minor enhancements to logging to be more descriptive especially with aliasified folders
• Refactoring to core libs for easier maintenance

🪲 Bug Fixes

• fix paths to pre and post deployment scripts when executed without repository #954
• support publishing artifacts greater than 5 MB #967
• sfdx sfpowerscripts:orchestrator:prepare shows errors in GitHub-Action #955
• Fail to fetch requested information when query is too long #860
• Display folder used while deploying to an org in aliasified mode
• Publish to tag packages that are successfully published even when other packages are failed
• Fix log times to display milliseconds, when source packages are being built. It usually displays as 00:00:00
• Support lwc subdirectories as reported in #959

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

April 22 - 4

Hotfix for sfpowerscripts to v13.0.15

fix(publish): fix issue when publishing artifacts bigger than 5 MB

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

April 22 - 3

Hotfix for sfpowerscripts to v13.0.14

• fix(validateagainstorg): validateImpl doesnt return any results, so the exit code is incorrect #950

Full Changelog: April22-2...April22-3

April 22 - 2

Hotfix for sfpowerscripts to v13.0.12, update to docker image

• Fixes for #936 and #933 in docker image definition
• fix(npx): remove npx in front of sfdx commands #939

Full Changelog:

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

April 22 -1

This is a hotfix for sfpowerscripts(v13.0.11) and sfp-cli(v2.0.9) for the following

• Fix copying of forceignore files when used outside a root directory (#932)
• Fix to ignore setting source tracking files during validate #931

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

April 22

sfpowerscripts(v13.0.9) features the following

💣 Breaking Changes

• Changes to the SFDX CLI source tracking #817, Require sfdx-cli 7.144.2 and above. We now support the latest source tracking enhancements released by the salesforce cli team.
• We are migrating sfpowerscripts to utilize underlying libraries open source by salesforce cli team, as opposed to wrapping around cli commands. We have completed the migration for most of the areas. You can read more about it here

⭐ New Features

• During validate, sfpowerscripts will automatically retry test class that fail in asynchronous mode to be executed synchronously. You can read the decision record on how it works here
• Introducing 'testSynchronous' , a new property which will let sfpowerscripts know that whether to execute a particular package in synchronous mode. This allows validation to be run in different modes for different packages
• Signed Docker Images served from ghcr.io. Read more on it here

⭐ Enhancements

• Add an option to Pool Configuration for scratch org creation time #903
• Add an environment variable SPFOWERSCRIPTS_DEFAULT_SHELL to select shell #873
• Clear code coverage and existing test result before test execution #871
• Add support for diffcheck parameter in validateAgainstOrg command #800
• Improved display of contents of a package #553

🪲 Bug Fixes

• Display artifacts installed in the order of committed #929
• Remove unsupported entities from sfdx-project.json #921
• Prepare command failing due timeout #893
• Override API version for unlocked and source package installation #885
• Error Plugin: @dxatscale/sfpowerscripts: Cannot find module 'node:process' #874
• Orchestrator Deploy Error TypeError: Cannot read properties of null (reading 'match') #872
• Fail to Install sfpowerscripts in a 'M1' powered Mackbook #864
• Fix for misleading error message for prepare cmd #851
• orchestrator validate step getting different code coverage from the same ci pool [#836](#836)
• Add support for api version in source convert #884

February 22 - 1

This is a hotfix for sfpowerscripts(v10.2.15) and sfp-cli(v0.0.47) for the following

• Failing to delete scratch org after validation (#838)
• Add devHubId to auth file used for scratch org authentication by @aly76 in #839

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

February 22

February 22 features the following

• sfpowerscripts (v10.2.13)
• sfp-cli (v0.0.45)

What's new

This release features the beta version of sfp-cli, a CLI for developers who utilizes DX@Scale in their projects. We hope this would simplify adoption of DX@Scale practices in your projects by combining git and sfdx into a single workflow

Fixes

• fix: validation of artifact source repo by @aly76 in #812
• fix(create-unlocked-package): provide valid error message when package creation is timing out by @azlam-abdulsalam in #832
• fix(npm-scope): converts npm scope to lowercase during publish and fetch by @azlam-abdulsalam in #833

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

December 21-5

Hotfix for bug occurring on fetching artifacts in orchestrator:prepare/release on Gitlab

• fix: orchestrator:prepare fails in GitLab Cloud Runners during SO Pool for updated artifact versions (#811)

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

December 21-4

Hotifix for bug occurring on dependency analysis in orchestrator:validate, which causes the command to break when dependencies field is undefined for an unlocked package.

• fix(dependency-analysis): handle case where dependencies field is undefined by @aly76 in #802

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