Add several scripts to run through the 2GP workflow from initial package creation to version release.
Scripts:
bootstrap-package.sh: Begin development on a new package; This script will run the appropriate sfdx command and also create a new "empty" directory for the module at project root level. Files for the new package would then fall under this new sub-folder.
create-package-version.sh: Used to generate new build versions of an in-development package. The subsequent new package build can then be manually installed into a test org or there is an option to continue to automated installation into a test scratch org.
install-test-package.sh: Generates a temporary scratch org for testing and installs the most recently created package build.
prep-release-package.sh: Runs through the pre-release flow to ready a package for new version release, including automatic installation into one final test org.
NOTES: 1) only one release per MAJOR.MINOR.PATCH version of a package is allowed, 2) the script in its current form assumes that the dev has updated package config in sfdx-project.json with the new version information (see "versionNumber" property).
Add several scripts to run through the 2GP workflow from initial package creation to version release.
Scripts:
bootstrap-package.sh
: Begin development on a new package; This script will run the appropriate sfdx command and also create a new "empty" directory for the module at project root level. Files for the new package would then fall under this new sub-folder.create-package-version.sh
: Used to generate new build versions of an in-development package. The subsequent new package build can then be manually installed into a test org or there is an option to continue to automated installation into a test scratch org.install-test-package.sh
: Generates a temporary scratch org for testing and installs the most recently created package build.prep-release-package.sh
: Runs through the pre-release flow to ready a package for new version release, including automatic installation into one final test org. NOTES: 1) only one release per MAJOR.MINOR.PATCH version of a package is allowed, 2) the script in its current form assumes that the dev has updated package config insfdx-project.json
with the new version information (see"versionNumber"
property).