Feature/build nuget without umbraco build #241
Draft
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
…uget-without-umbraco-build
[skip ci]
…aco-build' into feature/build-nuget-without-umbraco-build
change nuspecs
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.
@zpqrtbnk I am creating draf PR to show how I am handling creation of nuget packages base on devops yaml :)$project$ etc :)
I move nuspecs to be in path /project/Nuget as in my opinion it is better to have them like, as that show more clearly where belong nuspecs and simplifing getting needed files instead of using magic variables
simplify paths for files
remove dependency on Umbraco Build
prepare script to automatically propagate version based on version from dll
prepare yaml to build packages(we need figure out if we want release pre-release version also automatically and to which feed if so)
prepare release pipelines