build(release): v5.10.0 (#1349)

* chore: fix link in contributing

* 5.10.0

* try using github_token

* update labeler for release branches

* update labeler for release branches

* docs: dependency dashboard

* confirm if the permission was the magic

* re-introduce permission

---------

Co-authored-by: Adam Setch <[email protected]>

.github/labeler.yml

@@ -2,30 +2,42 @@ version: v1
 
 labels:
   - label: 'enhancement'
+    sync: true
     matcher:
       title: '^feat(\(\w+\))?: .*'
 
   - label: 'bug'
+    sync: true
     matcher:
       title: '^fix(\(\w+\))?: .*'
 
   - label: 'refactor'
+    sync: true
     matcher:
       title: '^refactor(\(\w+\))?: .*'
 
   - label: 'documentation'
+    sync: true
     matcher:
       title: '^docs(\(\w+\))?: .*'
 
   - label: 'test'
+    sync: true
     matcher:
       title: '^test(\(\w+\))?: .*'
 
   - label: 'build'
+    sync: true
     matcher:
-      title: '^(ci|build)(\(\w+\))?: .*'
+      title: '^(ci|build)(\((?!release)\w+\))?: (?!.*\brelease\b).*'
+
+  - label: 'release'
+    sync: true
+    matcher:
+      branch: '^release/.*'
 
   - label: 'dependency'
+    sync: true
     matcher:
       title: '^(deps)(\(\w+\))?: .*'
 
@@ -42,4 +54,5 @@ checks:
         - documentation
         - test
         - build
-        - dependency
+        - dependency
+        - release

.github/workflows/release.yml

@@ -33,6 +33,7 @@ jobs:
           APPLEID_TEAM_ID: ${{ secrets.appleid_teamid }}
           CSC_LINK: ${{ secrets.mac_certs }}
           CSC_KEY_PASSWORD: ${{ secrets.mac_certs_password }}
+          GH_TOKEN: ${{ secrets.github_token }}
           NOTARIZE: true
       - uses: actions/upload-artifact@v4
         with:
@@ -57,6 +58,8 @@ jobs:
           OAUTH_CLIENT_ID: ${{ secrets.oauth_client_id }}
           OAUTH_CLIENT_SECRET: ${{ secrets.oauth_client_secret }}
       - run: pnpm make:win --publish onTagOrDraft
+        env:
+          GH_TOKEN: ${{ secrets.github_token }}
       - uses: actions/upload-artifact@v4
         with:
           name: Gitify-release-win
@@ -80,6 +83,8 @@ jobs:
           OAUTH_CLIENT_ID: ${{ secrets.oauth_client_id }}
           OAUTH_CLIENT_SECRET: ${{ secrets.oauth_client_secret }}
       - run: pnpm make:linux --publish onTagOrDraft
+        env:
+          GH_TOKEN: ${{ secrets.github_token }}
       - uses: actions/upload-artifact@v4
         with:
           name: Gitify-release-linux

CONTRIBUTING.md

@@ -55,12 +55,13 @@ pnpm test -- --watch
 The release process is automated. Follow the steps below.
 
 1. Verify that all features you want targeted in the release have been merged to `main`.
-2. Create a [new **draft** release][github-new-release]. Set the tag version to something with the format of `v1.2.3`. Save as a **draft** before moving to the next step
-3. Create a branch that starts with `release/vX.X.X` (ie. `release/v1.2.3`).
-4. In the same branch, **bump the version** of the app by running `pnpm version <new-version-number`. Commit these changes and open a PR. A GitHub Actions workflow will build, sign and upload the release assets for each commit to that branch as long as a branch is named like `release/vX.X.X` and there is a draft release with the same version number(`package.json`).
-5. Merge your release branch into `main`.
-6. Publish the release once you've finalized the release notes and confirmed all assets are there.
-7. A new homebrew cask will be automatically published (workflow runs ~3 hours)
+2. Check the [Renovate Dependency Dashboard](https://github.com/gitify-app/gitify/issues/576) to see if there are any updates you want included.
+3. Create a [new **draft** release][github-new-release]. Set the tag version to something with the format of `v1.2.3`. Save as a **draft** before moving to the next step
+4. Create a branch that starts with `release/vX.X.X` (ie. `release/v1.2.3`).
+5. In the same branch, **bump the version** of the app by running `pnpm version <new-version-number`. Commit these changes and open a PR. A GitHub Actions workflow will build, sign and upload the release assets for each commit to that branch as long as a branch is named like `release/vX.X.X` and there is a draft release with the same version number(`package.json`).
+6. Merge your release branch into `main`.
+7. Publish the release once you've finalized the release notes and confirmed all assets are there.
+8. A new homebrew cask will be automatically published (workflow runs ~3 hours)
 
 ### Project Philosophy
 
@@ -79,3 +80,4 @@ This project is a tool for monitoring new notifications from Github. It's not me
 <!-- LINK LABELS -->
 [biome-website]: https://biomejs.dev/
 [jest-website]: https://jestjs.io/
+[github-new-release]: https://github.com/gitify-app/gitify/releases/new

README.md

@@ -34,7 +34,6 @@ For more information, see [LICENSE](LICENSE).
 [github]: https://github.com/gitify-app/gitify
 [github-actions]: https://github.com/gitify-app/gitify/actions
 [github-releases]: https://github.com/gitify-app/gitify/releases/latest
-[github-new-release]: https://github.com/gitify-app/gitify/releases/new
 [github-website]: https://github.com/gitify-app/website
 [github-website-pulls]: https://github.com/gitify-app/website/pulls
 [brew]: http://brew.sh/

package.json

@@ -1,6 +1,6 @@
 {
   "name": "gitify",
-  "version": "5.9.0",
+  "version": "5.10.0",
   "description": "GitHub Notifications on your menu bar.",
   "main": "src/electron/main.js",
   "scripts": {