Add instructions about release procedure #99
Merged
Conversation
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
tomaz-s1
approved these changes
Nov 6, 2023
Contributor
tomaz-s1
left a comment
tomaz-s1
left a comment
There was a problem hiding this comment.
LGTM.
Eventually we could also fully automate the release workflow as we have done for the Grafana plugin - https://github.com/scalyr/scalyr-grafana-datasource-plugin/blob/master/.github/workflows/release.yml#L92
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.
🥅 Goal
Add instructions about the release procedure.
🛠️ Solution
Instructions are added:
When code is merged, new tag is created and content of the release
folder is updated with the tarball containing the latest version. You can release
new version by following these instructions:
Generate release notes.TA_dataset-x.y.z.tar.gz.Publish release.🏫 Testing
Check the instructions.