Move to GitHub Actions and NuGet Trusted Publishing#740
Move to GitHub Actions and NuGet Trusted Publishing#740304NotModified wants to merge 9 commits intocastleproject:masterfrom
Conversation
Test resultsruns of latest commit on this PR: cd91f2a 6.0 preview releaseHow would 6.0 look like?
Looks all good: All packages are valid and are determenistic, source link and release mode 
6.0.1How would a release after 6.0 look like?
Correct numbers: Correct versions: |
|
This is ready for review. All tested with my fork :) We could even merge this without finishing the trusted publishing in #739 (comment) - but of course we could not release without it. |
|
|
||
| - name: Push to NuGet.org | ||
| if: inputs.publish == 'true' | ||
| run: dotnet nuget push artifacts\*.nupkg --api-key ${{steps.login.outputs.NUGET_API_KEY}} --source https://api.nuget.org/v3/index.json --skip-duplicate No newline at end of file |
There was a problem hiding this comment.
Cannot test this, but it's the same as https://github.com/NLog/NLog.MailKit/blob/master/.github/workflows/nuget.yml and see the run: https://github.com/NLog/NLog.MailKit/actions/runs/22880027311/job/66380506002
Updated changelog with new features, bug fixes, and migration to GitHub Actions.
Updated changelog to reflect changes in project structure and bug fixes.
Updated changelog with recent enhancements and bug fixes.
|
Ah! I was thinking, I could also test the condition. And there was a mistake, fixed it! See failing push when publish=true
|
2 participants
Changes from @Romfos, #700:
New changes:
I know this PR has a bit more then strictly necessary, but all these things are just great changes and makes the build/setup beter to maintain (no old build scripts etc.). I will make sure it will be all tested well.
How to use:
Fixes #739, fixes #497
Supersedes #700, supersedes #669