Release script added to create release/release candidates #844
Conversation
| # 1) Fetch the current release version | ||
|
|
||
| echo "Fetch tags" | ||
| git fetch --prune origin +refs/tags/*:refs/tags/* |
There was a problem hiding this comment.
I ended up changing this line from the original because I noticed that --prune was not working if I had deleted tags in github.
|
Gonna test this out in a fork when I get a chance. It might take me a bit to review. |
There was a problem hiding this comment.
@J-Thompson12 I get this error on my machine (Ubuntu with a regular terminal):
$ ./tools/tag-release.sh -p
Fetch tags
Current version: 0.3.0
./tools/tag-release.sh: line 115: unexpected EOF while looking for matching `"'
./tools/tag-release.sh: line 117: syntax error: unexpected end of fileLet me know if you can reproduce
@jpellizzari I was able to reproduce the error. It was caused by the extra ". Not sure how I put that in there. It wasnt in the forked version i was testing on. Its gone now and working. |
|
|
||
| if [ ! -z $release ] | ||
| then | ||
| if [[ $version == *"rc"* ]]; then # If the last version was not a release candidate then exit |
There was a problem hiding this comment.
👍 Really clever work on this part. I love the "promotion" UX. Very simple and elegant.
remove extra " Co-authored-by: Jordan Pellizzari <jordan@weave.works>
J-Thompson12
force-pushed
the
release-script
branch
from
91d729d
to
5b63284
Compare
…endencies (#854) * Fix spurious regex DoS vulnerability * Only scan production node modules for vulnerabilities * Turn auditing back on
Closes: #638
What changed?
Adds a script to tag/create releases and release candidates
Why?
How did you test it?
Manually on a fork.
Release notes
Documentation Changes
In the PR