You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* These conditions are set to allow a patch release, which will be the latest, to be made without the need to merge into master (normalizing how patch releases are done, always via the 'cut' action)
85
+
*
86
+
* Strangely before, if mergeFinal was true a checkout was performed and then a push was made, which didn’t make sense because in theory mergeFinal is when merging into master (it was redundant but didn’t cause any issues)
87
+
*
88
+
* Today, we want that if the action is `cut` and the version is a patch, the merge should be performed, the pull request will automatically be closed, and the release will be made.
89
+
* However, if the `cut` is for a pre-release version, the merge to master should not be performed, because minor/major releases are still done manually.
90
+
*
91
+
* by `mergeFinal` we can know it was triggered by a pull request merge to master
92
+
*/
80
93
81
-
// if the action is "cut" on a branch that will be the next release, we need to merge the changes to master
82
94
if(!mergeFinal&&isLatestRelease){
83
95
// get current branch name
84
96
constbranchName=awaitgetCurrentBranch();
85
97
86
98
// merge release changes to master
87
99
awaitcheckoutBranch('master');
88
100
awaitmergeBranch(branchName);
101
+
102
+
awaitpushChanges();
103
+
104
+
awaitcheckoutBranch(branchName);
89
105
}
90
106
91
107
core.info('fix dependencies in workspace packages');
@@ -102,7 +118,7 @@ export async function publishRelease({
0 commit comments