Now that TriPSs/conventional-changelog-action supports prereleases, we are moving away from our fork.
This PR also adds support for the create-github-release workflow to be used for both manual and automated releases. Currently, each of our repos have a manual-release.yml that duplicates most of the logic in githubRelease.yml. Having a shared workflow will make updating that shared logic much easier in the future. See an example of the new shared workflow that will be updated in all repos here: https://github.com/salesforcecli/testPackageRelease/blob/main/.github/workflows/create-github-release.yml
Adds enhanced support for prereleases, see testing scenarios below
ALSO, updates a couple external actions that were using the deprecated set-output commands. I pulled both actions locally and reviewed the code for mischief. Code looked good, packages are legit, and built files were not tampered with.
Migration plan:
Since create-github-release is a new workflow file, we can migrate our plugins over one by one
After all repos have been moved, remove the githubRelease.yml file
Announce in #platform-cli and #platform-dev-tools that the old file has been removed with instructions to migrate.
Now that
TriPSs/conventional-changelog-actionsupports prereleases, we are moving away from our fork.This PR also adds support for the
create-github-releaseworkflow to be used for both manual and automated releases. Currently, each of our repos have amanual-release.ymlthat duplicates most of the logic ingithubRelease.yml. Having a shared workflow will make updating that shared logic much easier in the future. See an example of the new shared workflow that will be updated in all repos here: https://github.com/salesforcecli/testPackageRelease/blob/main/.github/workflows/create-github-release.ymlAdds enhanced support for prereleases, see testing scenarios below
ALSO, updates a couple external actions that were using the deprecated
set-outputcommands. I pulled both actions locally and reviewed the code for mischief. Code looked good, packages are legit, and built files were not tampered with.Migration plan:
create-github-releaseis a new workflow file, we can migrate our plugins over one by onegithubRelease.ymlfile#platform-cliand#platform-dev-toolsthat the old file has been removed with instructions to migrate.Testing Scenarios for releases
maindevif you forget to set one.prerelease/**branch https://github.com/salesforcecli/testPackageRelease/pull/11/commits/dcebf2df630bc8b99024e18097dd6d53a9a5ac65devrelease: https://github.com/salesforcecli/testPackageRelease/actions/runs/54661965001.47.0)! https://github.com/salesforcecli/testPackageRelease/actions/runs/5466298231mainif we forgot semantic commits