add gh workflow for updating clarity-js-sdk #2107
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
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Adds a new GH Action workflow which creates a PR in the clarity-js-sdk repo to update the clarity-native-bin tag reference in source code. This GH action will run anytime a new release is published, so it should automatically hook into our current release process through the stacks-blockchain GH workflow.
The PR created will be auto-assigned to @hstove and @zone117x, and will need to be approved & merged.
Contributes to closing stacks-archive/clarity-js-sdk#99
Once this is merged, I'll need to work on automating the NPM publish for clarity-js-sdk to close the above ticket.
cc: @friedger
Type of Change
Does this introduce a breaking change?
No
Are documentation updates required?
No