Repository navigation
chore: prepare release 1.0.0-beta.1 - #15
Merged
Merged
Conversation
Describe the toolkit as it is today in the README, which is also the NuGet package page: the Sync status application, installation and registration, the 1.0.0-beta.1 version matrix, and absolute links. Add an install step to the Usage Guide and set local builds to 1.0.0-beta.1.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Prepares the first release,
1.0.0-beta.1.Changes
1.0.0-beta.1(runtime-verified on 30.8.0 and 31.9.1), and uses absolute links, since NuGet.org doesn't resolve relative ones.Directory.Build.props: local builds are1.0.0-beta.1(the release workflow sets the version from the tag either way).Testing
1.0.0-beta.1locally: MIT license, icon, README and XML docs included; the only dependency isKentico.Xperience.Admin30.8.0 or newer.Before tagging
nuget-releaseGitHub environment doesn't exist yet. GitHub creates a missing environment without protection when the workflow runs, so a tag would publish without the manual approval Release-Process.md requires. Create it with a required reviewer first.release.ymland thenuget-releaseenvironment.