fix: release branch workflow (#6)

cdk8s-team · Sep 21, 2021 · 78f5fcb · 78f5fcb
1 parent 46e5488
commit 78f5fcb
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 9 deletions.
diff --git a/.github/workflows/release-k8s.22.yml b/.github/workflows/release-k8s.22.yml
diff --git a/.projen/tasks.json b/.projen/tasks.json
diff --git a/.projenrc.js b/.projenrc.js
@@ -15,7 +15,7 @@ function k8sVersion() {
     // so assume that we are building for the latest version, i.e. 1.22.0
     console.log(
       'Warning: The current branch name doesn\'t start with "k8s-XX", so we ' +
-      `are defaulting to built for k8s 1.${DEFAULT_K8S_VERSION}.0. If you ` +
+      `are defaulting to build for k8s 1.${DEFAULT_K8S_VERSION}.0. If you ` +
       'did not intend for this, please rename your branch to start with "k8s-XX/", ' +
       'where XX is the intended k8s version.',
     );
@@ -61,7 +61,7 @@ const project = new JsiiProject({
   majorVersion: 1,
   releaseTagPrefix: `cdk8s-plus-${SPEC_VERSION}/`,
   releaseWorkflowName: `release-k8s.${SPEC_VERSION}`,
-  defaultReleaseBranch: `k8s.${SPEC_VERSION}`,
+  defaultReleaseBranch: `k8s-${SPEC_VERSION}/main`,
   minNodeVersion: '12.13.0',
 
   // jsii configuration

diff --git a/package.json b/package.json