[STR-335] Automate SDK publishing#24
Merged
frostbournesb merged 6 commits intodevelopfrom Feb 13, 2023
Merged
Conversation
Collaborator
|
Collaborator
|
ocasta181
previously approved these changes
Feb 9, 2023
ocasta181
approved these changes
Feb 9, 2023
saito-sv
approved these changes
Feb 10, 2023
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
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.
Late last night, I worked on making an automated script to make sure that we never mess up
cd scripts-- You must run it from the scripts folder, for nowRun
python3 publish.pyto view the help screenDon't worry about running it, it will run a dry run first then ask you if you want to publish
It will cache your .env so don't worry about changing that back
It will save a backup of your package.json before it changes anything, so you can see if it messed up
Use -u to use your fingerprint PK from .env
If you don't use it, you will need to put it in env-dev.txt or env-prod.txt (don't gitignore them, it will automatically remove it after running)
It will handle automatically incrementing the version, use -s if you want to manually change the version and use that.