1.8 KiB
1.8 KiB
name | about | title | labels | assignees |
---|---|---|---|---|
Release Process | Maintainers Only - Release Process | Release Process for v6.x.x | Issue-Meta |
Release Process for v6.x.x
- Verify that
PowerShell-Native
has been updated/released as needed. - Check for
PowerShellGet
andPackageManagement
release plans. - Start process to sync Azure DevOps artifacts feed such as modules and NuGet packages.
- Create a private branch named
release/v6.x.x
in Azure DevOps repository. All release related changes should happen in this branch. - Prepare packages
- Build release packages
- Sign the MSI packages and RPM package.
- Install and verify the packages.
- Trigger the docker staging builds (signing must be done.)
- Run tests on all supported Linux distributions and publish results
- Update documentation, and scripts.
- Update CHANGELOG.md with the finalized change log draft.
- Update other documents and scripts to use the new package names, links, and
metadata.json
.
- Create NuGet packages and publish them to
powershell-core
feed. - Run release build to publish Linux packages to Microsoft YUM/APT repositories.
- Create the release tag and push the tag to
PowerShell/PowerShell
repository. - Run release build to create the draft and publish the release in Github.
- For preview releases,
merge the release branch to Github
master
with a merge commit. - For non-preview releases, make sure all changes are either already in master or have
- Delete the release branch.
- Trigger the docker image release.
- Test and publish NuGet packages on NuGet.org
- Retain builds.