Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: nuget packing in release-dotnet-native.yaml #524

Merged
merged 16 commits into from
Nov 9, 2023
Merged

Conversation

mhmd-azeez
Copy link
Collaborator

@mhmd-azeez mhmd-azeez commented Oct 18, 2023

Seems like there are some weird subtle differences between Windows and Linux

@mhmd-azeez mhmd-azeez changed the title fix: typo in fetch-tags in release-dotnet-native.yaml fix: nuget packing in release-dotnet-native.yaml Oct 18, 2023
@mhmd-azeez
Copy link
Collaborator Author

image

@mhmd-azeez
Copy link
Collaborator Author

mhmd-azeez commented Oct 18, 2023

Comment on lines +45 to 51
- name: Pack NuGet packages
run: |
find ./dotnet/nuget -type f -name "*.csproj" -exec dotnet pack {} -o release-artifacts \;

- name: Publish NuGet packages
run: |
dotnet pack .\dotnet\nuget\Nuget.sln -o release-artifacts
dotnet nuget push --source https://api.nuget.org/v3/index.json ./release-artifacts/*.nupkg --api-key ${{ secrets.NUGET_API_KEY }}
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chrisdickinson

Great work! Landing this and following up by splitting the dotnet pack creation from the dotnet nuget push steps is perfect.

Is this what you meant?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I'm late in responding! Not quite – I meant splitting the dotnet pack step into a separate workflow that creates a draft GitHub release on push to main or tag creation, then modifying the release workflow that triggers on GitHub release to dotnet nuget push the artifact from the release. (Splitting out these steps moves us in this direction, though – the PR LGTM!)

@mhmd-azeez
Copy link
Collaborator Author

Let's merge this PR and then I will try to integrate it into the main flow

Comment on lines +45 to 51
- name: Pack NuGet packages
run: |
find ./dotnet/nuget -type f -name "*.csproj" -exec dotnet pack {} -o release-artifacts \;

- name: Publish NuGet packages
run: |
dotnet pack .\dotnet\nuget\Nuget.sln -o release-artifacts
dotnet nuget push --source https://api.nuget.org/v3/index.json ./release-artifacts/*.nupkg --api-key ${{ secrets.NUGET_API_KEY }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I'm late in responding! Not quite – I meant splitting the dotnet pack step into a separate workflow that creates a draft GitHub release on push to main or tag creation, then modifying the release workflow that triggers on GitHub release to dotnet nuget push the artifact from the release. (Splitting out these steps moves us in this direction, though – the PR LGTM!)

@mhmd-azeez
Copy link
Collaborator Author

@chrisdickinson perfect, I will open a separate PR

@mhmd-azeez mhmd-azeez merged commit 2fb2902 into main Nov 9, 2023
3 checks passed
@mhmd-azeez mhmd-azeez deleted the mhmd-azeez-patch-1 branch November 9, 2023 07:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants