December 23

Time flies! and thanks to everyone who contributed to sfp this year. It was monumental, we reached more users with more orgs actively approaching modular development like never before

We wrap the final release of the year and wish you all a prosperous new years.

December 23 (v25.5.3) of sfp introduces the following changes, and this release is mainly possible due to all of our contributions! Keep it coming!

⭐ New Features

• feat(validate) : Always use the newest validation scratch org during Validate by @alanjaouen in #1428

🪲 Bug Fixes

• fix(README): contributors link target dx@scale repo by @alanjaouen in #1424
• fix(workItemfilters): Support multiple workItem filters by @brandonmikeska in #1429
• fix(orgInfo): display login URL instead of instance URL for scratch orgs by @michallachowski in #1432
• fix(docs): Update example commands and typos by @crazynammer in #1431
• fix(docs): some typos in documentation and comments by @nabondance in #1433
• fix(apex-test): additional parallel run error by @jdrbc in #1436
• feat(install): Specify testLevel for a not optimized source package validating by @nabondance in #1434
• fix(deploy):Honor waitTime for Deploy commands by @brandonmikeska in #1443
• fix(picklist): Bug fix for picklist Deployment by @cjbradshaw in #1442

New Contributors

• @brandonmikeska made their first contribution in #1429
• @crazynammer made their first contribution in #1431
• @jdrbc made their first contribution in #1436

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/sfpowerscripts@25.0.6...@dxatscale/sfpowerscripts@25.5.3

October 23

October 23(v25.0.6) features the following

⭐ New Features

• feat(install): introduce a unified package installation command #1420

sfp features a new command called sfp package:install which can auto determine the type of a package and proceed to install in an environment. This allows users to easily install a package into an environment without using the individual package commands. The individual commands now carry a deprecation notice and will be removed from future releases

• feat(docker): use node 18 LTS instead of the latest 20.x version

We have downgraded the docker image to use LTS version of node rather than the latest, as there was some issues noted with certain plugins. Also @rody and @ethan-sargent was able to reduce the size of the image by 1.5Gigs, this results in quicker download. Thanks a heap guys!

• feat(browserforce): Updated browserforce to dxatscale fork

Browserforce is temporarily switched to a dxatscale fork, with the latest salesforce dependencies, We plan to submit the changes to the main stream in a short while. You might need to use --targetusername in your script if you are using the same.

🪲 Bug Fixes

• fix(picklist): PicklistEnabler errors out if picklist doesn't exist on target org #1414 . Thanks @cjbradshaw for figuring out the issue and the fix
• fix(packagediff): fix packages being built when the path to package start with same structure. Fixes #1396. Thanks @thraco
• fix(help): Fix help segments not getting displayed when using sfp topic in terminal
• Minor bug fixes in error handling in apex tests

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/sfpowerscripts@24.5.0...@dxatscale/sfpowerscripts@25.0.6

August 23

August23 (v24.5.0) features the following

Update to the the docker image is the key highlight for this release, We have started using ubuntu 22 as the base image as opposed to Salesforce CLI base image, due to the root issue as discussed in #1409. Finally, profile merge/retrieve makes a comeback and is available in sfp. Now you can really deprecate sfpowerkit :)

⭐ New Features

• feat:(profiles) profile merge and retrieve is reintroduced to sfp #1353
• feat(output) sfp features more richer output in .sfpowerscripts/logs folder in markdown formats, This is a work in progress feature which enables one to link markdown formatted output to your CI/CD platforms or notification platforms like Slack or Teams

🪲 Bug Fixes

• fix(schema): update schema to remove warning around seedMetadata #1400
• fix(package): install using v58.0 PackageInstallRequest parameters #1370
• fix(pool): enable json flag for pool fetch command #1404
• fix(docker):use lower uid in dockerfiles #1409
• fix(apextests): handle conditions where test results are inaccurate from salesforce
• fix(diff): throw error if an associated meta file is missing in repository such as *.meta-xml for a changed file such as .cls
• fix(diff): diff package not correctly copying static resources

New Contributors

• @ruslan-kurchenko made their first contribution in #1370
• @nvuillam made their first contribution in #1401
• @RobinWeymans made their first contribution in #1404

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/sfpowerscripts@23.4.2...@dxatscale/sfpowerscripts@24.5.0

July 23

July23(v23.4.2) features the following

This release we focused mainly on updating to v5 @salesforce/core and updating many of the dependencies (#1366 and #1388). This will help you close many of the issues that your security team has been pestering you with on deprecated dependencies. Though sfpowerscripts is not used in the context of web application and many vulnerabilities are not really applicable, updating to the latest dependencies reduces so much friction in usage in the enterprise.

Special thanks to @rygramer for the fantastic effort in raising issues which helped to fix these dependencies easily.
Another contributor that needs a special mention is @petter-eikeland, who has taken additional effort to test Release Candiates.

⭐ New Features

• Enhancements to transitive dependency resolver to support multiple version #1226

🪲 Bug Fixes

• PicklistAnalyzer errors out if other other non CustomField Metadata is processed first #1367
• Bad namespaced class names from apex-node break test retry logic #1362
• fix(triggerApexTests): second test run results are not merged #1360
• sfp orchestrator:validate with Code Coverage Validation #1359
• validate fails to build package when fht is enabled during fast feedback mode #1358
• sfp orchestrator:build - Language bug upon package version creation [#1347](#1347)
• orchestrator:release --dryrun still attempts to install packages [#1340](#1340)
• orchestrator:build job removes too many packages from queue after single failure #1199

❤️ Contributors

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

• @Schuchie
• @rygramer
• @JonnyPower

June 23 - Patch 1

June 23 Patch (v 22.6.1) is a patch for an issue for picklist deployments.

What's Changed

• fix(picklist-support): fix check for empty records on org by @Rocko1204 in #1341
• feat(release): add an option to skip artifact record update in release|
  Add a new property called skipArtifactUpdate which allows for skipping insertion of artifact versions to sfpowerscripts_artifact2__c. This is useful in case of diff packages where hotfix deployments should not alter the version already recorded. A better variant of this will be
  released at later stage

New Contributors

• @Rocko1204 made their first contribution in #1297

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/sfpowerscripts@22.5.5...@dxatscale/sfpowerscripts@22.6.1

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/sfpowerscripts@21.1.0...@dxatscale/sfpowerscripts@22.5.5

April 23

April 23 (v21.1.0) features the following

💣 Breaking Change

validate command will now respect aliasified packages. This means aliasified packages which do not have a default directory will fail during validation. To fix this, either ignore the package or add a default directory to the aliasified package which is the contents that you want to deploy to the scratch origin

Enhancements

• feat(validate): validate will no longer display deployment options #1295
• feat(metrics): new splunk metrics sender by @Rocko1204 in #1297

🪲 Bug Fixes

• fix(links): add $schema properties #1203
• fix(fht): rollbackOnError need to be true for production #1299
• fix(validate): aliasified packages are ignored in validate by #1293

New Contributors

• @Rocko1204 made their first contribution in #1297

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/sfpowerscripts@20.30.4...@dxatscale/sfpowerscripts@21.1.0

March 23 - Patch 1

v20.30.4 is a patch for the following issue

• fix(installunlocked): incorrect length matching by @azlam-abdulsalam in #1285. Thanks @alanjaouen for the detailed issue report

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/sfpowerscripts@20.30.3...@dxatscale/sfpowerscripts@20.30.4

March 23

sfpowerscripts (v20.30.3) introduces the following new features more towards bringing release configuration everywhere. Release configuration can now be applied in prepare, build and deploy providing more flexibility especially when you have multiple independent teams

⭐ New Features

• feat(deploy): deploy to support release config #1264

Deploy command now has an option to support release config, Thanks @alanjaouen for providing a detailed analysis on why this is required

• feat(build): add support for release config to build #1272
• feat(deploy): enable source tracking support for deploy command #1273
• feat(publish): Add new flag to delete Git tags by age and limit minimum #1275

🪲 Bug Fixes

• fix(prepare): ensure prepare in build mode respects releaseconfig by @azlam-abdulsalam in #1281
• fix(delete): Fix typo in message for when no Scratch Orgs are found by @JoeffreyChaucer in #1283
• fix(fetch): SFDX Org List recognizes fetched scratch orgs as non-scratch orgs. Thanks @petter-eikeland for following it up.

New Contributors

• @JoeffreyChaucer made their first contribution in #1275

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/sfpowerscripts@20.26.3...@dxatscale/sfpowerscripts@20.30.3

Release - February 2023 Patch 1

sfpowerscripts(v 20.26.3) fixes the following issues

What's Changed

• fix(releasedefn-generator): release defn generator to build packages that are not tagged by @azlam-abdulsalam in #1261
• fix(deploy): ensure max retry count is set to 10 by @azlam-abdulsalam in #1263

Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/sfpowerscripts@20.26.2...@dxatscale/sfpowerscripts@20.26.3