Automate release branch creation
See original GitHub issueWe need to perform the following tasks every time we create a release-*.*
branch:
- TypeScript creates a branch from
master
on GitHub. - TypeScript updates the version on that branch to
beta
.- Update
package.json
- Update
src/compiler/corePublic.ts
- Update
- TypeScript LKGs the branch.
- SDK script is updated to sync from that branch.
We should find a way to do all of this “at once”.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Using Github Actions to Automate Our Release Process
Check out code from app repo. · Create new release branch named release/v{versionName} · Change the version name and version code of release....
Read more >How to automate git version release of master branch?
Enter new version (Current 1.0.5): 1.0.6 Are you sure you want to release version 1.0.6? (y|n): y Switched to a new branch 'release-1.0.6' ......
Read more >Using git-flow to automate your git branching workflow
git-flow is a library of git subcommands that helps automate your branching and release workflow workflow, using Vincent Driessen's ...
Read more >Automate merging release branches into your main branch ...
A typical release process for Git workflows involves creating a release branch, performing various tests on that branch, and applying any ...
Read more >Automating Releases with GitHub Workflows - Conor Strejcek
In any case, when you reach this point, it's time to cut a release branch. Following the git-flow model, this is normally a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There is now a
@typescript-bot create release-X.Y
task that can be used in issues. Ideally, it should be used in a release tracking issue (where anything to do pertaining to the upcoming release process can be collected).I can prepare tasks for the other common release branch activities, like syncing with
master
(for pre-RC), doing an LKG (if a cherry-pick-and-LKG command on a PR is insufficient), changing the release tag+version (from0-beta
to0-rc
to.1
, to.2
and beyond), and, hopefully, triggering the final publish task.With all that in place, all we should need is appropriate triggers for the VS SDK builds, right?
I think the tag happens after all of this - there still may be changes in the release branch before the beta tag is created