Releases: dxatscale/sfpowerscripts
October 21 - 1
Hotfix release to address the below issue
Full Changelog: https://github.com/Accenture/sfpowerscripts/compare/@dxatscale/[email protected]...@dxatscale/[email protected]
October 21
⭐ New Features
- Support for 'default' folder in aliasify packages #715
🐞 Bug Fixes
- Source packages with apex classes and profiles fail to deploy if reconcileProfiles is enabled #717
- Hard-coded user.email value in Changelog code causes git push failure #710
- Allow prepare to go ahead when artifacts are not yet published #706
- Unable to fetch deployment failure report for Source packages with failed test classes #705
- Quickbuild - "Invalid time value" - error #697
- Production org that is not a Dev Hub is falsely identified as sandbox for testing purposes on source deployment #720
❤️ Contributors
Thanks @bjanderson70 for raising issues #710 and #697
September 21
⭐ New Features
- Add Header to fetch command #648
- Improve sfpowerscripts: package create output #626
- Add Chalk Support #475
- Analyze PMD should provide options on when to break build #432
- Sample Pipelines for Jenkins, Circle CI, Drone.. #366
🪲 Bug Fixes
- Require --branchname parameter when generating a release changelog #671
- Release commands not reporting detailed metrics #645
❤️ Contributors
We'd like to thank all the contributors who worked on this release!
August 21 - 5
Fixes #665 - hanging on scratch org creation
August 21 - 4
#662 (v 8.1.18) Fix incorrect output shown for Apex tests, in some cases where the request failed
August 21 - 3
This version (v8.1.17) features a hotfix for the following bug
#655 Fix console output for package:[type]:create commands
August 21 - 2
This version (v 8.1.14) is a hotfix for the following bug
#650 Deploy command was not reporting error messages during failure.
August 21 - 1
This release (v8.1.13) is a hotfix to fix PMD analysis in sfpowerscripts.
Fixes
- #644 Fix Broken PMD Analysis
August 21
The Aug 21' (v8.1.10) release includes a couple of breaking changes. Developer pools are now available in sfpowerscripts, with most of the orchestrator:prepare
command flags being moved and consolidated in a configuration file. Enable source tracking in the pool configuration file to persist source tracking files to the scratch orgs - providing developers with an experience as if the scratch orgs were created entirely on their own machines. That means improved productivity, as developers only need to deploy their own changes to the scratch orgs. The other breaking change involves the SFDMU plugin, which must be updated to version 4.4.0 or later in order to work with sfpowerscripts.
Check out 'sfpowerscripts orchestrator pool breaking changes' article for more information.
💥 💥 Breaking Changes
⭐ Enhancements
- Check for existence of configuration files for data packages #621
- Add a noColor option to disable colors #584