Build Unstable NuGet packages #3889
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
crobibero
approved these changes
Aug 13, 2020
daullmer
changed the title
joshuaboniface
approved these changes
Aug 24, 2020
joshuaboniface
approved these changes
Aug 25, 2020
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.
Changes
With this PR merged, every commit to master builds unstable nuget packages. They don't get pushed to any Nuget feeds. To achive this, I added the
VersionPrefixproperty to every .csproj file which outputs Nuget packages and integrated the version number into the bump_version script.I changed the Nuget pack CI task to the .Net Core pack Task because of this note in the docs
Issues
This allows for easier plugin development before we publish the stable version because we can make changes to the plugins during the release cycle.