Closed drewnoakes closed 5 months ago
Now that we're moving to building and pushing packages via GitHub actions
The first run of this just completed successfully.
This is a huge improvement over the previous manual release process.
Every 12 months I'll need to refresh the NuGet API key in this repo's secrets.
Validated package contents and metadata, including SourceLink and determinism:
@iamcarbon once you're happy with the changes for 2.9.0 (especially API-changes) we can push out a release.
Now that we're moving to building and pushing packages via GitHub actions, we will take the version from the release itself. This means we don't want it to be specified in the file directly.
I like this change as it means we don't have to keep the props file in sync with the current version, simplifying the release process somewhat. We only have to bump the version in the README which directs users to install the current version. That can always be done after release if missed.