feature: implement version change PR (#676)

* update readme with notes about character limits and designating bumps

* edit PR template to note addition of a change file

* add change file for #674

* add change file for #673

* add change file for #672

* add change file for #671

* add version action

* set version command in config

* add change file for #677

* add labels to PRs

* Update .changes/tauri-info-crash.md

Co-authored-by: Rajiv Shah <rajivshah1@icloud.com>

* Update .changes/HttpRequestBuilder-implementation.md

Co-authored-by: Rajiv Shah <rajivshah1@icloud.com>

* Update kill-beforeDevProcess-on-shutdown.md

* Update reflect-conf-changes.md

Co-authored-by: Rajiv Shah <rajivshah1@icloud.com>
Co-authored-by: Lucas Fernandes Nogueira <lucasfernandesnog@gmail.com>

.changes/HttpRequestBuilder-implementation.md

@@ -0,0 +1,5 @@
+---
+"tauri-api": minor
+---
+
+This adds HttpRequestBuilder, described at "alternatives you've considered" section in [#651](https://github.com/tauri-apps/tauri/issues/651).

.changes/config.json

@@ -1,9 +1,11 @@
 {
   "pkgManagers": {
     "rust": {
+      "version": true,
       "publish": false
     },
     "javascript": {
+      "version": true,
       "publish": false
     }
   },

.changes/kill-beforeDevProcess-on-shutdown.md

@@ -0,0 +1,5 @@
+---
+"tauri.js": patch
+---
+
+Kill process started by `tauri.conf.json > build > beforeDevCommand` on CLI shutdown.

.changes/readme.md

@@ -15,3 +15,15 @@ Use the following format:
 Change summary goes here
 
 ```
+
+Summaries do not have a specific character limit, but are text only. These summaries are used within the (future implementation of) changelogs. They will give context to the change and also point back to the original PR if more details and context are needed.
+
+Changes will be designated as a `major`, `minor` or `patch` as further described in [semver](https://semver.org/).
+
+Given a version number MAJOR.MINOR.PATCH, increment the:
+
+- MAJOR version when you make incompatible API changes,
+- MINOR version when you add functionality in a backwards compatible manner, and
+- PATCH version when you make backwards compatible bug fixes.
+
+Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format, but will be discussed prior to usage (as extra steps will be necessary in consideration of merging and publishing).

.changes/reflect-conf-changes.md

@@ -0,0 +1,6 @@
+---
+"tauri.js": patch
+"tauri": patch
+---
+
+Properly reflect tauri.conf.json changes on app when running `tauri dev`.

.changes/tauri-hot-reload-regression.md

@@ -0,0 +1,5 @@
+---
+"tauri.js": patch
+---
+
+Fixes regression on hot reload when Rust doesn't compile.

.changes/tauri-info-crash.md

@@ -0,0 +1,5 @@
+---
+"tauri.js": patch
+---
+
+Fixes the case when `tauri info` is run and a project has not yet created a `Cargo.lock` closing [#610](https://github.com/tauri-apps/tauri/issues/610).

.github/PULL_REQUEST_TEMPLATE.md

@@ -32,6 +32,7 @@ If yes, please describe the impact and migration path for existing applications
 
 - [ ] It's submitted to the `dev` branch and _not_ the `master` branch
 - [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix: #xxx[,#xxx]`, where "xxx" is the issue number)
+- [ ] A change file is added if any packages will require a version bump due to this PR per [the instructions in the readme](https://github.com/tauri-apps/tauri/blob/dev/.changes/readme.md).
 
 If adding a **new feature**, the PR's description includes:
 - [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

.github/workflows/pr-to-master.yml

@@ -27,6 +27,7 @@ jobs:
           branch: release/master
           branch-suffix: short-commit-hash
           title: Publish
+          labels: "publish"
           body: |
             Merging this PR will squash and push all changes to the master branch.
             It will kick off the process to release and publish any packages with an incremented version number.

.github/workflows/pr-version-updates.yml

@@ -0,0 +1,32 @@
+name: pr-version-updates
+
+on:
+  push:
+    branches:
+      - dev
+
+jobs:
+  pr-to-master:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: git config
+        run: |
+          git config --global user.name "${{ github.event.pusher.name }}"
+          git config --global user.email "${{ github.event.pusher.email }}"
+      - name: covector version
+        uses: jbolda/covector/packages/action@master
+        id: covector
+        with:
+          command: 'version'
+      - name: Create Pull Request With Versions Bumped
+        uses: tauri-apps/create-pull-request@v2.8.0
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          branch: release/version-updates
+          title: Apply Version Updates From Current Changes
+          labels: "version updates"
+          body: |
+            Merging this PR will update the versions on all packages with changes as specified in the `.changes` directory.
+            It will kick off the process to release and publish any packages with an incremented version number.