Automate version release process for 2.x branch #2653
Conversation
I added a "git_tag" to package.json, name can be changed to something else but it's used to replace the tag url and name in README.md Also I don't believe last_version is used anymore and can be removed
|
The inspection completed: No new issues |
|
Does this work? |
|
I think. I can't test the whole thing without doing a release. It's based on acknowledge-me's deploy script, which works swiminigly. |
|
Let's test it this week for Pods 2.5.2 release. Tomorrow or Friday should work. What's the process? |
|
So we have to put the old_version as whatever the alpha version was in 2.x branch, right? |
|
@sc0ttkclark Oops those docs are behind the improvements @jamesgol did. All we have to do now is changes version in package.json and git_tag in package.json and run |
|
So the steps leading up to running this, should be:
Or do 2 and 3 get switched, or is that all part of it? |
|
@sc0ttkclark I updated those docs, will make into real docs later tonight or tomorrow. But yes you are right. This is designed to happen after we merge 2.x into master. It updates version numbers, commits that, tags the master branch, and then pushes all to GitHub and WPORG SVN. I can walk you through it when we do it. |
|
Great, I'll setup the 2.5.2 PR. |
|
Closeing as #joshfail will redo |
resolves #2648