chore(repo): Update changesets PR title (#3414)

clerk · May 21, 2024 · c5ecc2f · c5ecc2f
1 parent 62f8af2
commit c5ecc2f
Show file tree

Hide file tree

Showing 4 changed files with 7 additions and 4 deletions.
diff --git a/.changeset/cuddly-hotels-judge.md b/.changeset/cuddly-hotels-judge.md
@@ -0,0 +1,2 @@
+---
+---
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -55,7 +55,8 @@ jobs:
         id: changesets
         uses: changesets/action@v1
         with:
-          commit: 'chore(repo): Version packages'
+          commit: 'ci(repo): Version packages'
+          title: 'ci(repo): Version packages'
           publish: npm run release
           # Workaround for https://github.com/changesets/changesets/issues/421
           version: npm run version

diff --git a/docs/CICD.md b/docs/CICD.md
@@ -9,7 +9,7 @@ Every time a PR is merged into `main`, an automated canary release will happen.
 
 ## Stable releases
 
-A stable release will be triggered every time the "Version Packages" PR is merged. Once versioning and publishing is done, the `clerk/javascript` repo will dispatch a workflow event, notifying other related Clerk repos of the new releases.
+A stable release will be triggered every time the "ci(repo): Version packages" PR is merged. Once versioning and publishing is done, the `clerk/javascript` repo will dispatch a workflow event, notifying other related Clerk repos of the new releases.
 
 Actions that will be triggered:
 

diff --git a/docs/PUBLISH.md b/docs/PUBLISH.md
@@ -6,9 +6,9 @@ _Note: Only Clerk employees can trigger the actions described below._
 
 We are using [changesets](https://github.com/changesets/changesets), so our CICD is using [`changesets/action`](https://github.com/changesets/action) to automate the release process when releasing stable package versions targeting the `@latest` tag.
 
-Every time a PR is merged into `main`, the changesets action parses all changesets found in `.changeset` and updates the "Version Packages" PR with the new package versions and the changelog for the next stable release.
+Every time a PR is merged into `main`, the changesets action parses all changesets found in `.changeset` and updates the "ci(repo): Version packages" PR with the new package versions and the changelog for the next stable release.
 
-To release a new stable version of all Clerk packages, find the "Version Packages" PR, verify the changes, and merge it.
+To release a new stable version of all Clerk packages, find the "ci(repo): Version packages" PR, verify the changes, and merge it.
 
 ## Publishing canary package versions (`@canary`)