November 22

sfpowerscripts(v20.2.4) features the following

💣 Breaking Changes

• Additional new modes for validate command.[#1133]

We heard you loud and clear, that you need flexibility with validate command depending on the type of repository and project configuration. On some projects you would need to limit your validation boundary, only validate a changed package etc, we support it all. Read more here https://docs.dxatscale.io/v/release-november-22/sfpowerscripts/validate#validate-modes

Unfortunately, that means we had to break up the command line parameters, a new flag called mode is added (defaults to thorough) to access other modes

⭐ New Features

• Create pools with a set of specified artifacts[#978]

Utilize release config (https://docs.dxatscale.io/v/release-november-22/sfpowerscripts/release/release-definition-generator#config-file) to limit the artifacts installed in scratch orgs and use the same in validate command. We would also like to thank @domrycz for contributing majority code for the feature and testing the early releases

• [Beta] 'validate' to identify fix incorrect transitive dependencies #855.

Add enableTransitiveDependencyResolver:true, to the plugins section of sfdx-project.json will enable this feature.

 "plugins": {
        "sfpowerscripts": {
            enableTransitiveDependencyResolver:true // enable transitive dependency resolution 
            "ignoreFiles": {
                "prepare": ".forceignore",
                "validate": ".forceignore",
                "quickbuild": "forceignores/.quickbuildignore",
                "build": "forceignores/.buildignore"
            }
        }
    }

• Utilize packaging lib for all package related operations, this removes the dependency on sfdx-cli #1121.

⭐ Enhancements

• Prepare command creates too many Scratch Orgs when using snapshot pool #1105 Thanks @domrycz for figuring out the missed scenario

🪲 Bug Fixes

• Issue when publishing "big" artifacts #1149. Thanks to @alanjaouen for raising the issue as well as PR to fix it
• Artifacts aren't pulled correctly releasedefinition:generate #1140 @Schuchie
• Scratch Org Pool creation script failing "Unable to execute command .. Error: Can't find package id for dependency: 04txxxx" #1113[eneag-sf] @eneag-sf
  Full Changelog: https://github.com/dxatscale/sfpowerscripts/compare/@dxatscale/[email protected]...@dxatscale/[email protected]

September 22

sfpowerscripts(v19.7.3) features the following

⭐ New Features

• Support for multiple release definitions

  Release command now supports multiple release definition as input. This allows a release manager to composite releases from different domains more easily and release them in a single transaction.

⭐ Enhancements

• Ability to skip all external package dependencies while generating a release definition

  When you are generating release definitions using multiple filters to composited later, external package dependencies might get repeated and it may also not be required for every files. Now release definition generator have an additional parameter
  excludeAllPackageDependencies:<boolean> to skip package dependencies being added to generated release defnitions.

• Utilize sfdx cli docker image as the base and minor docker improvements

  We are switching to utilising sfdx-cli as the base docker image. This reduces the image size and provides better stability in fixating on the version of the cli

• Makes logs more concise and easy to read

  Logs have been made much more concise to read and interpret in various commands. This will help in readability

• Auto Log Grouping

  Logs are now automatically grouped for Github Actions, Gitlab, Buildkite and Azure Pipelines even if the '-g (loggroup)' flag is not used

🪲 Bug Fixes

• Release fails if its unable to push a changelog
• If 2 failing test methods have the same name, they get removed from test results (#1111) Thanks @Chiqqn and @domrycz for raising the issue and fixing the same
• Incorrect Error Handling on Deployment Failure during validate (#1123)

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

August 22

sfpowerscripts(v19.4.1) features the following

⭐ New Features

• Generate Release Definition automatically

Last release we announced a beta version of 'releasedefinition:generate'. While the idea was solid, the command lacked flexibility and it was put back to the drawing board. This release we have created a whole new of way interacting with the command. Read more about it in the descision record here . Documentation is updated on how to use this command as well. Check out the link here. Thanks to @Schuchie for the feedback

• Support for distinct scratch org definitions

You might need to use this feature very rarerly, but if the need arises, you have it. This feature allows a user to specify a unique scratch org config file for building a package. When the feature is enabled and the package name is matched, the build command will use specified config file for that package. Read more about it here

⭐ Enhancements

• Enhanced Package Dependencies Installation

sfpowerscripts no longer utilise the 'sfpowerkit:package:dependencies:install' to install dependencies. A new implementation is being utilised by validate/prepare/release commands. This command utilise the same dependency resolver used by package and removes lot of technical debt.

• Change in dependencies installation order

validate will no longer install all the external dependencies upfront. External dependencies will only be installed if the required package has to be validated and it will be installed just in time. This will make help with further increasing the speed of validate especially in thorough mode and change in package dependencies

• Skip package installations if a higher version is already installed

sfpowerscripts will now skip external dependencies such as managed package thats gets automatically upgraded in the target org. Unfortunately this can only work after noticing a failed installation in the org and reading the error message. Read more about the discussion here (https://github.com/dxatscale/sfpowerkit/issues/602)

Installing Package Salesforce CPQ in [email protected]
A higher version of this package is already installed and cant be downgraded, skipping

• Add support for multiple work item filters in changelog

Release definition files now support multiple work item filters, using the `workItemFilters', which expect an array of regex pattern filters. The changelog will pick up work items that match all the patterns

🪲 Bug Fixes

• We have fixed few internal defects as well

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

July22 - 1

sfpowerscripts is updated to 18.1.5 to address the following issue

Bugfixes

• Downgrade sfdx data plugin to 2.0.0 in docker image #1085
• Fixes to changelog: generate command #1087

New Contributors

• @Schuchie made their first contribution in #1087

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

July 22

sfpowerscripts July release (18.1.3) features the following

⭐ New Features

• Handle Entitlements with ease, sfpowerscripts now feature a smart entitlement filtering. To read more on how it works. Follow the link here . Thanks @MengSQi for helping us with the implementation
• Support .NEXT for Source/Data Packages #1065. .NEXT will be replaced by build number during the build of source/data packages. This would remove the validation errors when you have forgotten to set the last digit as '0'
• Hooks for "Prepare" command via scripts #991. This allows to tweak the prepared scratch orgs further. Read more here
• [BETA Feature] Now generate release definition based on a source org. Try this command out and keep the feedbacks coming.
  

🪲 Bug Fixes

• Fix for #1075 skipTesting is not respected when optimizedDeployment is false. Thanks to @sumanth-bolledla-acn for the extensive tests on this one
• Fix for #942 scratch org creation now supports ObjectSettings

⚠️ Local Installation Advice (if not using docker)

We have migrated the underlying libraries to utilize @salesforce/core v3 and @jsforce: 2.0.0. Please uninstall existing plugin before installing the newer version.

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

June 22-1

Hotfix patch for the following issue

• fix(sfdx-cli): update sfdx-cli to 7.156.1 #1072

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

June 22

sfpowerscripts(v15.3.2) features the following

⭐ New Feature

• sfpowerscripts is now able to use multiple stages for prepare. This will help you to circumvent timeouts on cloud hosted agents of most ci/cd platforms. Read on more about the feature here https://docs.dxatscale.io/v/release-june-22/sfpowerscripts/orchestrator/prepare#using-prepare-in-multiple-stages. Also do check the decision record to understand the reasoning
  

⭐ Enhancements

• Return unused/rolled back scratch orgs to the pool #989. For this enhancement to work, please ensure sfpower-scratchorg-pool package is updated. Read on the instruction on how to update here
• Add info about optimised deployment during deployment #994
• Add support for unpackaged metadata in unlocked packages #958
• Ignore packages without a package name attribute #842
• Log resolved package dependencies during build #1058
• Additional metrics for individual scratch orgs in pool. Check metrics docs for details

🪲 Bug Fixes

• No clear error when package name exceeds 38 characters #998
• Provide more descriptive error message when it is unable to compute diff during build #965
• Warning message is not displayed when tests are skipped explicitly #919
• Incorrect Dependencies might be used during build stage #496
• No Metrics while using fast feedback

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

May 22-3

Hotfix for sfpowerscripts to v13.6.22 with the following fixes

What's Changed

• Unlocked package installation are failing due to PermissionSetGroup recalculation #1000

Thanks @dieffrei for raising the PR

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

May 22-2

Hotfix for sfpowerscripts to v13.6.21 with the following fixes to address some dependabot alerts

What's Changed

• update @salesforce/core to 2.37.1
• remove usage of shelljs in core
• update semver to 7.37.1

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

May 22 -1

Hotfix for sfpowerscripts to v13.6.18 with the following fixes

• Fix to select the correct testlevel while deploying to prod #993. Thanks to @mpaul1 for raising the issue
• Fix for release not to fail if a package is already promoted if retried

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