You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
D. Ror. edited this page Jun 16, 2026
·
7 revisions
By default the CI build-test action in GHA creates pre-release versions of the libpalaso nuget packages.
Official product releases should be based on a release version of the libraries. When a product team is preparing to release a new version of their product, they can create a new release of libpalaso following these steps:
Ideally, post something in the commonlibraries channel on Slack to give others a chance to finish off pending work that should be included in the release.
Add the new version number to CHANGELOG.md. Verify that all relevant changes are mentioned in the changelog.
Create a git tag with the new version, e.g. v8.0.0.
Manually run the build-test action in GHA, which will create the nuget packages and publish them on nuget.org.
Optional
Create a release on GitHub based on the git tag. Paste the text with the changes since the last release from CHANGELOG.md as
release notes.
Delete (hide) the now obsolete pre-release versions on nuget.org (e.g. once version X.0.0 is released we should hide the pre-release version X.0.0-pre-whatever to remove clutter). SIL.NuGetCleaner can be used to do that.