docs: update to v1.4 and add latest changes (#512)

## 📝 Description
Documentation change. Add e installation instructions for v1.4 on CE and
EE. Also add the latest changes:
- Notifications are only sent to users with access to the project
- Draft PR can be disabled
- There is a new Rebuild Pipeline button

Fixes #511

## ✅ Checklist
- [X] I have tested this change
- [ ] This change requires documentation update

Author: TomFern

docs/docs/using-semaphore/img/rerun-pipeline.jpg

@@ -29,6 +29,12 @@ Always use [Incoming Webhooks app](https://semaphore.slack.com/apps/A0F7XDUAZ-in
 
 To create a notification, navigate to **Notifications** and press **New Notification**
 
+:::note
+
+Notifications are only be sent to people with access to the project. If you are not receiving notifications, check if you have [access to the project](./rbac).
+
+:::
+
 <Steps>
 
 1. Type the name of the notification
@@ -103,6 +109,12 @@ At this point, you can create additional rules or save the changes by pressing *
 </TabItem>
 <TabItem value="cli" label="CLI">
 
+:::note
+
+Notifications are only be sent to people with access to the project. If you are not receiving notifications, check if you have at least [member access to the project](./rbac).
+
+:::
+
 To create a Slack notification, install and connect the [Semaphore command line](../reference/semaphore-cli) and execute:
 
 ```shell title="Creating an Slack Notification"
@@ -323,4 +335,4 @@ Sample `tag` object:
 ## See also
 
 - [How to create notifications using YAML](../reference/semaphore-cli#notifications)
-- [How to create notifications for flaky tests](./tests/flaky-tests#notifications)
+- [How to create notifications for flaky tests](./tests/flaky-tests#notifications)

docs/docs/using-semaphore/img/trigger-draft-pull-request.jpg

@@ -150,6 +150,16 @@ Here you can see the how spc evaluated the pipeline and all the actions taken du
 
 ![Example init job log](./img/init-log-example.jpg)
 
+## Pipeline rebuild {#rebuild}
+
+When a job in the pipeline fails, the default behavior is to stop the pipeline. You can attempt to re-run the pipeline in two ways:
+
+- Pressing **Rerun** restarts the whole pipeline from the beginning
+- Pressing **Rebuild Pipeline** only re-runs the blocks with failed jobs
+
+![Location of rerun and rebuild buttons](./img/rerun-pipeline.jpg)
+
+
 ## Connecting pipelines with promotions {#connecting-pipelines}
 
 Your project can have multiple pipelines to perform different tasks such as build, release, or test. [Promotions](./promotions) connect pipelines. Multiple pipelines can be chained to create branching workflows to automate almost any task.

docs/docs/using-semaphore/notifications.md

@@ -65,23 +65,23 @@ const config = {
               banner: "none",
             },
             "CE": {
-              label: 'Community Edition v1.3',
+              label: 'Community Edition v1.4 (latest)',
               path: 'CE',
               banner: "none"
             },
-            "CE-1.2": {
-              label: 'Community Edition v1.2',
-              path: 'CE-1.2',
-            },
-            "CE-1.1": {
-              label: 'Community Edition v1.1',
-              path: 'CE-1.1',
+            "CE-1.3": {
+              label: 'Community Edition v1.3',
+              path: 'CE-1.3',
             },
             "EE": {
-              label: 'Enterprise Edition v1.3',
+              label: 'Enterprise Edition v1.4 (latest)',
               path: 'EE',
               banner: "none"
             },
+            "EE-1.3": {
+              label: 'Enterprise Edition v1.3',
+              path: 'EE-1.3',
+            },
           },
 
         },