June 23
June 23 (v22.5.5) features the following
💣 Breaking Change
Transition from sfdx plugin to npm module:
sfpowerscripts has transitioned from a Salesforce DX plugin to an npm module. It should now be installed using the command npm i -g @dxatscale/sfpowerscripts.
The commands can be used directly, e.g. sfpowerscripts orchestrator:build ---
. For a shorter alias, use sfp instead of sfpowerscripts.
sfpowerscripts is now independent of sfpowerkit
The new sfpowerscripts no longer relies on sfpowerkit for functionality. Any functionality that sfpowerscripts used to depend on sfpowerkit has been ported over.
Deprecations
- This version discontinues the sfp-cli due to low usage.
- The commands sfpowerscripts analyze:pmd and sfpowerscripts package:valid are no longer available.
- vbt cli is no longer available in the docker image
Enhancements
Support for Picklist Deployment
sfpowerscripts now supports picklist deployment. This feature addresses Salesforce's limitation of not allowing picklist values to be deployed during unlocked package upgrades. Read more about it here https://medium.com/@gnemiq/deploy-picklists-from-unlocked-packages-102c1366664f
Support for Branches in package depdency (#1270 )
sfpowerscripts now supports branch attributes in dependencies, picking up the right dependencies of external packages from the right branches when being installed
Introduction of a 'Diff' Package Type
sfpowerscripts now offers a 'Diff' package type designed to facilitate organizations' transition from a monolithic structure to a modular DX@Scale model. A Diff package captures the differences in unpackaged metadata from the previous deployment, deploying only the delta. This approach allows unpackaged sections of the project to be deployed alongside packaged modules in a controlled manner .
Please note, this feature is still in early development, Please reach out if you have queries on how to use it
🪲 Bug Fixes
- fix(apexlink): direct conversion to json breaks on large packages by @azlam-abdulsalam in #1306
- fix(schema): new attributes in sfdx-project.json will result in warning as opposed to errors #1329
- fix(orginfo): add front door display url to logint to the sandbox (0562998)
- fix(analyzer): display the analyzer being used in pre/post analyzers
- fix(sfpowerscripts): validate not reporting additional tags
Validate and validateAgainstOrg was not reporting metrics correctly, as it was not hooked up with proper events. This change request fixes the same and also passes in release config
New Contributors
- @marcelosousa made their first contribution in #1319
Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/[email protected]...@dxatscale/[email protected]