Skip to content

Updated Renovate docs. #2361

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlexSkrypnyk merged 1 commit into from
Mar 12, 2026
Merged

Updated Renovate docs. #2361

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 27 additions & 15 deletions .vortex/docs/content/tools/renovate.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,21 +10,33 @@ The configuration is stored in [`renovate.json`](https://github.com/drevops/vort
based on [Renovate configuration for automated Drupal dependency updates](https://github.com/drevops/renovate-drupal)
project.

## Features

1. Dual schedules for Drupal package updates (root `composer.json` only):
- Daily update schedule for critical Drupal core and related packages created in
the `deps/drupal-minor-patch-core` branch.
- Weekly update schedule for all other packages created in
the `deps/drupal-minor-patch-contrib` branch.
2. npm/yarn package updates (root `package.json` only) in the `deps/npm-minor-patch` branch.
3. Container image updates in `.docker/` directory in the `deps/docker` branch.
4. GitHub Actions updates in the `deps/github-actions` branch.
5. Automatically adds a `dependencies` label to a pull request.
6. Automatically adds assignees to a pull request.
7. Configuration for running Renovate self-hosted instance using CircleCI.
8. Manual trigger from GitHub Actions UI and CircleCI pipeline.
9. Debug logging enabled for detailed troubleshooting.
## How updates are organized

All Renovate PRs use the branch prefix `deps/` and are labeled `Dependencies`.
Assignees can be configured in the `assignees` field.
Comment on lines +15 to +16
Copy link

@coderabbitai coderabbitai bot Mar 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Consider clarifying where the assignees field is located.

Line 16 mentions the assignees field but doesn't specify where it should be configured. Adding a reference to renovate.json would help users unfamiliar with Renovate configuration.

📝 Suggested clarification 
 All Renovate PRs use the branch prefix `deps/` and are labeled `Dependencies`.
-Assignees can be configured in the `assignees` field.
+Assignees can be configured in the `assignees` field in `renovate.json`.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
All Renovate PRs use the branch prefix `deps/` and are labeled `Dependencies`.
Assignees can be configured in the `assignees` field.
All Renovate PRs use the branch prefix `deps/` and are labeled `Dependencies`.
Assignees can be configured in the `assignees` field in `renovate.json`.
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In @.vortex/docs/content/tools/renovate.mdx around lines 15 - 16, Clarify that
the `assignees` field referenced on the line about Renovate is part of
Renovate's configuration (e.g., the repository-level renovate.json) by updating
the sentence to explicitly say something like "Assignees can be configured in
your Renovate configuration (e.g., the repository's renovate.json)"; reference
the `assignees` field name and the renovate.json file so readers know where to
set it.


### Update rules

| Group | Packages | Update types | Schedule |
|---|---|---|---|
| **Drupal core** | `drupal/core-recommended`, `drupal/core-composer-scaffold` and other `drupal/core-*` packages | Minor, patch | Daily before 2 AM UTC |
| **Drupal contrib and PHP packages (non-core)** | All Drupal contrib modules and non-Drupal Packagist packages | Minor, patch | Weekly, Sunday before 2 AM UTC |
| **JS packages** | All npm packages (root `package.json` only) | Minor, patch | Weekly, Sunday before 2 AM UTC |
| **Container images** | All images in `.docker/` and `docker-compose.yml` | Major, minor, patch | Daily before 3 AM UTC |
| **GitHub Actions** | All actions (pinned to digests) | Major, minor, patch | Daily before 3 AM UTC |

### Disabled updates

These are intentionally skipped by Renovate — update them manually:

| Group | What is skipped | Why |
|---|---|---|
| Drupal core major | `drupal/core-recommended`, `drupal/core-composer-scaffold` and other `drupal/core-*` packages | Major version upgrades may introduce breaking changes |
| PHP and Drupal contrib major | All Drupal contrib modules and non-Drupal Packagist packages | Major version upgrades may introduce breaking changes |
| JS major | All npm packages | Major version upgrades may introduce breaking changes |
| PHP language version | `php` constraint in `composer.json` | Major version upgrades may introduce breaking changes |
| JS language versions | `node`, `yarn` in `package.json` | Major version upgrades may introduce breaking changes |
| JS non-root packages | Any `package.json` not at the root | Theme dependencies are managed separately |

## Self-hosted vs GitHub app

Expand Down
Loading