build: prepare v5.13.0 release (#1476)

* 5.13.0

* build: prepare `v5.13.0` release

Signed-off-by: Adam Setch <adam.setch@outlook.com>

* build: prepare `v5.13.0` release

Signed-off-by: Adam Setch <adam.setch@outlook.com>

* build: drop snap support - was never working

Signed-off-by: Adam Setch <adam.setch@outlook.com>

---------

Signed-off-by: Adam Setch <adam.setch@outlook.com>

Author: setchy

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -38,6 +38,7 @@ body:
       label: Gitify Version
       description: What version of Gitify are you using?
       options:
+        - 5.13.0
         - 5.12.1
         - 5.12.0
         - 5.11.0

.github/workflows/build.yml

@@ -4,7 +4,6 @@ on:
   push:
     branches:
       - main
-      - 'release/v**'
   pull_request:
     branches:
       - main

CONTRIBUTING.md

@@ -57,16 +57,18 @@ 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. Check the [Renovate Dependency Dashboard][github-dependency-dashboard] 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. Edit current [Milestone][github-milestones] to have: 
+4. Create a branch that starts with `release/vX.X.X` (ie. `release/v1.2.3`).  In this branch you need to:
+  * Run `pnpm version <new-version-number` to **bump the version** of the app . 
+  * Update `./github/ISSUE_TEMPLATE/bug_report.yml` to have the new app version.
+  * 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. Edit current [Milestone][github-milestones] to have: 
    * description: link to the release notes
    * due date: date of release
    * close milestone
-9. Create a [New Milestone][github-new-milestone] for upcoming release.
-10. A new homebrew cask will be [automatically published][homebrew-cask-autobump-workflow] (workflow runs ~3 hours)
+8. Create a [New Milestone][github-new-milestone] for upcoming release.
+9. A new homebrew cask will be [automatically published][homebrew-cask-autobump-workflow] (workflow runs ~3 hours)
 
 ### Project Philosophy
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "gitify",
-  "version": "5.12.1",
+  "version": "5.13.0",
   "description": "GitHub Notifications on your menu bar.",
   "main": "src/electron/main.js",
   "scripts": {
@@ -93,7 +93,7 @@
       "oneClick": false
     },
     "linux": {
-      "target": ["AppImage", "deb", "rpm", "snap"],
+      "target": ["AppImage", "deb", "rpm"],
       "category": "Development",
       "maintainer": "Emmanouil Konstantinidis"
     },