Remove release workflow #134
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
Uzlopak
previously approved these changes
Mar 18, 2022
|
Sorry @Uzlopak can you re-approve, forgot to set |
Uzlopak
approved these changes
Mar 18, 2022
|
Erledigt. |
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.
Summary
This removes the unused release workflow that would automatically deploy the release to npm and github poackages.
We will later include it when there is a) consensus whetjher we want to automate releases or not and b) a working implementation that runs after all checks have completed.
Note: this does not affect the unit tests and integration test as these were defined in own workflow files.
Linked issue(s)
#36
Involved parts of the project
CI
Added tests?
OAuth2 standard
Reproduction