Merge branch '4' into 5.0

silverstripe · Jul 31, 2023 · 1a73935 · 1a73935
2 parents ee0923d + 747e844
commit 1a73935
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/en/02_Developer_Guides/19_GraphQL/01_getting_started/02_configuring_your_schema.md b/en/02_Developer_Guides/19_GraphQL/01_getting_started/02_configuring_your_schema.md
@@ -136,7 +136,7 @@ There are two approaches to namespacing:
 
 ##### Namespacing by filename
 
-If the filename is named one of the four keywords above, it will be implicitly placed
+If the filename is named one of the seven keywords used in the `app/_graphql/schema.yml` example above, it will be implicitly placed
 in the corresponding section of the schema - e.g. any configuration
 added to `app/_graphql/config.yml` will be implicitly added to
 `SilverStripe\GraphQL\Schema\Schema.schemas.default.config`.
@@ -171,7 +171,7 @@ will not work).
 
 ##### Namespacing by directory name
 
-If you use a parent directory name (at any depth) of one of the four keywords above, it will
+If you use a parent directory name (at any depth) of one of the seven keywords, it will
 be implicitly placed in the corresponding section of the schema - e.g. any configuration
 added to a `.yml` file in `app/_graphql/config/` will be implicitly added to
 `SilverStripe\GraphQL\Schema\Schema.schemas.default.config`.

diff --git a/en/05_Contributing/04_Release_Process.md b/en/05_Contributing/04_Release_Process.md
@@ -305,6 +305,7 @@ This rating determines which release lines are targeted with security fixes.
 | **High**      | 7.0 to 8.9 | Important releases should be evaluated immediately. These issues allow an attacker to compromise a site's data and should be fixed within days. *Example: SQL injection.* |
 | **Medium**    | 4.0 to 6.9 | Releases of moderate severity should be applied as soon as possible. They allow the unauthorized editing or creation of content. *Examples: Cross Site Scripting (XSS) in template helpers.* |
 | **Low**       | 0.1 to 3.9 | Low risk releases fix information disclosure and read-only privilege escalation vulnerabilities. These updates should also be applied as soon as possible, but with an impact-dependent priority. *Example: Exposure of the core version number, Cross Site Scripting (XSS) limited to the admin interface.* |
+| **None**      | 0.0 | These releases won't affect a large majority of projects, and may not require any action. They only impact projects with extremely complex or unlikely customisations. They do not impact projects which only implement common customisations or use common features. |
 
 ### Internal Security Process