Pack and upload artifacts for release builds #220
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
glopesdev
added
feature
glopesdev
force-pushed
the
release-automation
branch
from
81151dd
to
af50464
Compare
glopesdev
force-pushed
the
release-automation
branch
2 times, most recently
from
9cdd7a0
to
faeffaa
Compare
aspaNeuro
approved these changes
Jul 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a first step in building a release automation workflow, this PR conditions the
Packstep on the release output and collects the final generated NuGet packages as part of the action output.Appropriate pre-release suffixes are automatically generated for both local and CI builds to prevent name clashes.