Releases: dxatscale/sfpowerscripts
July21 - 1
sfpowerscripts v7.1.20
A quick fix for pre/post execution scripts that was broken due to an incorrect fix applied earlier. Thanks to @nbatterham for pointing this out.
July21
Release July21 (v 7.1.19) features the following changes.
⭐ New Features
-
Migrate sfpowerscripts artifact record to use custom settings #476
We are migrating sfpowerscripts artifact package to utilize a new CustomSettings based Object instead of the one currently utilized. This is to ensure artifact records are being copied when a sandbox is being refreshed. sfpowerscripts is backward compatible with the change and would still work with the exiting object. However, we recommend you move to the latest version of the sfpowerscripts artifact package. Head over to https://github.com/Accenture/sfpowerscripts/tree/develop/prerequisites/sfpowerscripts-artifact for the new package ID (if you are utilizing pre-built package) or find the source code to build the unlocked package by yourself.
🪲 Bug Fixes
- Missing Orchestrator:Release Command Glossary #565
- No indication of reason after validate job deployment failure (reopened) #557
- Inaccurate package coverage percentage on validate #556
- Pre/Post Execution scripts are logged into console during pooling #541
- An aliasified package should be auto ignored in Validate stage or alternate mechanism to be provided #444
As usual, thanks to all our users and contributors!
Release 23
This release contains non-backwards compatible changes to the release changelog and promote command, that allow a new release branch to reuse artifacts from the source branch.
The release changelog no longer works with the artifact source branch, instead users need to input the branch. This prevents the changelog from being incorrectly written to the source branch when generating a changelog on a release branch.
The 'promote' command does not mutate artifacts anymore and the --outputdir flag has been deprecated. An additional option has been added to the release definition that allows promotion before deployment to a specific org. Only unlocked packages are promoted and required to be promoted before installing to a production environment.
🪲 Bug Fixes
Release 22.3
A minor patch update which include the fix to the following
- #525 Show name and context on package validation fail. Thanks to @LawrenceLoz for the fix.
Also please note sfpowerscripts is only compatible with sfdmu 4.2.6, higher versions fail on deployment to prod. We are working on a fix in the next release
Release 22.2
A hotfix (v6.0.1) for a race condition identified when pushing changelog back to the repository
🪲 Bug Fixes
- Fix merge conflict when multiple instances are pushing changelog #518
Release 22.1
This is an interim plus hotfix (v6.0.0) where we had to add functionality to enable release notes to work with any type of authentication mechanism used by agent. It was limited to SSH in the last release. This resulted in some breaking changes to the existing changelog generator and also adds hotfixes on org update status
🪲 Bug Fixes
Release 22
Release 22 (v 5.6.0) features the following new features, enhancements and bug fixes
⭐ New Features
- Introduce a notion of release into sfpowerscripts #452💥
- Graduate changelog generator to prod status #333💔 (breaking)
- Native support for Datadog metrics #505
It's been worth the wait! We have the release command that lets you create release easily without using fetch and deploy. Also, it produces a beautiful changelog with org badges. This also introduces a breaking change to the build command making branch a mandatory flag.
Enhancements
- Add support for checkpoints in prepare #509
- Additional orchestrator support to prevent flaky scratch orgs in the pool.
- Validate sfdx-project.json #497
- Thanks @dieffrei and many others for requesting this, We now validate the sfdx-project.json for any incorrect properties, as it was the source of many errors
- Add a reporting table for build #486
- Build now displays the reason why the package is being picked up.
🪲 Bug Fixes
Hotfix-2 for Release 21
This is a hotfix for Release 21 (v 4.4.12) which features the following fix
🐞 Bug Fixes
- In cases such as prepare, multiple orgs are being provisioned at the same time, so each org needs to have its query result for installed artifacts stored #481
Hotfix for Release 21
This is a hotfix for Release 21 (v 4.4.11) which features the following fix
🐞 Bug Fixes
- Org Dependent unlocked package was incorrectly checked for test coverage. #469
Release 21
Release 21 (v4.4.10) features the following, major highlight being supporting private npm package registries simplyfiying artifact management
⭐ New Features
- Add support for fetching artifacts by introducing a fetch command in artifacts topic #440
- Fail early during deployment to production if using non promoted packages #428 --breaking
- Add an option to create npm compatible packages. #418
- Deploy latest artifact version #414
- Allow SARIF as a format for PMD Analysis #407
- Log Based Metrics #362
🪲 Bug Fixes
- Fail creation of unlocked package when test coverage is below 75% #457
- Display Error message while unable to fetch type of package #439
- Only check if packages are installed at the start of Deploy, and not in each individual package installation #437
- Fail when apext tests are not available #416
- Show text exec error instead of missing test report error #411
- .next not supported for source/data packages #405
- Skip changelog generation for duplicate release names #464
❤️ Contributors
We'd like to thank all the contributors who worked on this release!