GitHub Actions: upload nupkg as artifact

[janusw]

Note: I'm using git describe --tags to generate a unique version number for each package that is built. This scheme will also generate a proper version for a release, if the corresponding tag is set.

[janusw]

The nupkg generated for this PR is here: https://github.com/GeoJSON-Net/GeoJSON.Net/actions/runs/8071855382#artifacts

It obtained the version 1.2.15-28-g01bab48, since 1.2.15 seems to be the last tag present in the repository (and there were 28 commits since then). Tags for all later versions seem to be missing.

[xfischer]

Hi @janusw and thanks for that. So if I understand well, this is a first step towards prelease package automation, and automatic nuget publish ? Did I miss something ?

EDIT : found the related discussion here : #167 (comment)

[janusw]

Hi @janusw and thanks for that. So if I understand well, this is a first step towards prelease package automation, and automatic nuget publish ? Did I miss something ?

Yes, basically. This is the way I handle packaging for some other libraries as well. Having a package built for every PR makes it much easier for users to test pre-release versions.

As written on the other thread, automatic publishing on nuget.org is certainly possible as well, but I'm not so sure if it's worth to go there. Once everything is automatically packaged and versioned, the final upload for publishing is really quick and simple.

For building a "release" package, once can simply set a tag for the release version (like "2.0.0"), and push it together with the final commit (or re-trigger the CI after pushing the tag). Then GHA will use the correct version 2.0.0 for the package, and it can be directly uploaded to nuget.org.

[janusw]

Thanks for merging!