Skip to content

Commit

Permalink
chore(repo): Use clerk-v4 branch for staging and production releases
Browse files Browse the repository at this point in the history
Until clerk@v5 is ready for release we will be using
the clerk-v4 branch for staging and production releases
and every commit and changelog entry SHOULD be committed
in both clerk-v4 and main branches.
The main branch will be used to produce canary releases.
  • Loading branch information
dimkl committed Oct 17, 2023
1 parent 50d0497 commit 9106c31
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions .changeset/config.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"fixed": [],
"linked": [],
"access": "public",
"baseBranch": "origin/main",
"baseBranch": "clerk-v4",
"updateInternalDependencies": "patch",
"ignore": [],
"snapshot": {
Expand All @@ -16,4 +16,4 @@
"onlyUpdatePeerDependentsWhenOutOfRange": true,
"updateInternalDependents": "always"
}
}
}
2 changes: 1 addition & 1 deletion .github/workflows/release-prod.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ run-name: Production release PR
on:
push:
branches:
- main
- clerk-v4

concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/release-staging.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ run-name: Staging release from ${{ github.ref_name }}
on:
push:
branches:
- main
- clerk-v4

concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
Expand Down

0 comments on commit 9106c31

Please sign in to comment.