Merge branch 'main' into feat/rules

Author: eiriksm

docs/configuration/default_branch_security.mdx

@@ -0,0 +1,48 @@
+---
+title: "default_branch_security"
+---
+
+## Configuration
+
+<div className="config-wrapper"><div className="config">__name__: default_branch_security</div>
+<div className="config">__type__: string</div>
+<div className="config">__default__: ''</div></div>
+
+```json showLineNumbers
+{
+  "name": "company/project",
+  "extra": {
+    "violinist": {
+      // highlight-next-line
+      "default_branch_security": ""
+    }
+  }
+}
+```
+
+Indicate what branch you want the Violinist pull requests created against, spefically if the update is a security update.
+
+## Explanation
+
+Different projects uses different workflows for their branches. For example, your default branch in your VCS provider might be your production branch (for example `main`) while you want the merge requests to be created towards a development branch (for example `develop`). By default, Violinist will use the default branch for the repository to create the merge requests, but if you want the base branch to differ from this setting when merge requests are security updates, you want to use the `default_branch_security` option.
+
+## Example
+
+If a project uses the `develop` branch as the default branch, and you want the merge requests that are security updates to go straigth to `main`, you might want to configure your project like so:
+
+```json showLineNumbers
+{
+  "name": "company/project",
+  "description": "My awesome project",
+  "extra": {
+    "violinist": {
+      // highlight-next-line
+      "default_branch_security": "main"
+    }
+  }
+}
+```
+
+If you do not enter anything in this field, leaving the default value for it in there (`""` - an empty string) the project will use the settings from the project repository. In the example above that would mean the branch `develop`.
+
+Please also note that if you have a value for the configuration option [default_branch](/configuration/default_branch) then this will be used as a fallback for a default value of empty string (`""`) for this configuration option (`default_branch_security`).

docs/configuration/ignore_platform_requirements.mdx

@@ -0,0 +1,60 @@
+---
+title: "ignore_platform_requirements"
+date: 2026-01-25T10:00:00+01:00
+anchor: "ignore-platform-requirements"
+weight:
+---
+
+## Configuration
+
+<div className="config-wrapper"><div className="config">__name__: ignore_platform_requirements</div>
+<div className="config">__type__: int</div>
+<div className="config">__default__: 0</div></div>
+
+```json showLineNumbers
+{
+  "name": "company/project",
+  "extra": {
+    "violinist": {
+// highlight-next-line
+      "ignore_platform_requirements": 0
+    }
+  }
+}
+```
+
+Ignore PHP platform requirements when checking for updates.
+
+## Explanation
+
+When enabled, Violinist will set the `COMPOSER_IGNORE_PLATFORM_REQS` environment variable. This tells Composer to ignore platform requirements (PHP version, extensions, etc.) when resolving and updating dependencies.
+
+This can be useful when the PHP version or extensions available in Violinist's environment differ from your production environment.
+
+## Example
+
+Say your production environment uses a PHP extension that isn't universally available. Without this option, Composer might refuse to update packages because the extension isn't present when checking for updates. To work around this, enable `ignore_platform_requirements`:
+
+```json showLineNumbers
+{
+  "name": "company/project",
+  "description": "My awesome project",
+  "require": {
+    "php": "^8.2",
+    "ext-acme": "*",
+    "vendor/package": "~1.0.0"
+  },
+  "extra": {
+    "violinist": {
+// highlight-next-line
+      "ignore_platform_requirements": 1
+    }
+  }
+}
+```
+
+:::note
+`ext-acme` is a fictional extension used for illustration purposes.
+:::
+
+With this configuration, Violinist will ignore platform requirements and proceed with checking for updates. Your CI pipeline should still verify that the updated dependencies work correctly with your actual platform configuration.

package-lock.json

@@ -20,8 +20,8 @@
     "@mdx-js/react": "^3.1.1",
     "clsx": "^2.0.0",
     "prism-react-renderer": "^2.4.1",
-    "react": "^19.2.3",
-    "react-dom": "^19.2.3"
+    "react": "^19.2.4",
+    "react-dom": "^19.2.4"
   },
   "devDependencies": {
     "@docusaurus/module-type-aliases": "3.9.2",