Created nuget build workflow #312
Conversation
Net6.0 reached EOL, netstandard2.1 will still work with Net6.0 so we replace it with active LTS version net 8.0
Make project show a valid source link, include symbols and make build deterministic
This reverts commit f9cc385.
Create nuget_build_release
forgot file extension
Attempt at fixing release note creation
Forgot to enforce deterministic builds on net6.0 after revert.
…dotnet into nuget-push-workflow
Enforce embedded pdb and deterministric for every builds
Changed source for production nuget index
|
There was also a failed attemp at upgrading the EOL net6.0 to LTS net8.0 but this created a error due to new changes between the versions. Since It concerned the handling of files bytes, I decided to revert to prevent breaking anything. |
|
Thanks a bunch! I'll experiment with it and see what it can do.
Thanks. That's something else entirely. I'd rather decide when to make that jump. |
|
I just realised I made one small change into the wrong branch so it wasn't added to the pull request. It's mostly cosmetics so it won't cause any real issue, there was a badge added to the readme that redirected to the workflow file to allow easiers access to the build/publish logs
|
|
Sounds neat~ You can add it to a new PR; I still have an open issue to work on before next release. |
|
Awesome. Worked like a charm! Thanks man |
This pull request closes : #309
What changed:
The configuration of the ATL project (ATL.csproj) has been edited to include symbols file and make builds deterministic. Additionally, the package will now include this repo README file and uses the release note section to show changes. The content of the release note section is taken from the body/content of your published release. The version name is taken from the tag name of your published release. Note that the release section does not support markdown, as a work around we could remove the README file and continue using the README as the release note.
You can see a preview of the results here:
https://int.nugettest.org/packages/z440.atl.core/1.4.10
https://github.com/kitsumed/atldotnet/actions
You can also verify that builds do include symbols and are deterministic by manually downloading the nugettest.org package and selecting it on https://nuget.info/ (Under the File dropdown menu at the top)
What you need to do
The workflow uses a NuGet API key to push the package, that key is stored as a github secret (Repository) under the name
NUGET_API_KEY. I would recommend creating a API key with the smallest scope possible, in this case, restricted to only publishing update on the atl package.