build: configure renovate

.github/actionlint.yaml

@@ -0,0 +1,3 @@
+self-hosted-runner:
+    labels:
+        - ubuntu-26.04

.github/actions/ci/action.yaml

@@ -1,5 +1,5 @@
 name: CI checks
-description: Installs dependencies, checks formatting, lints Markdown and code, type checks, tests, and builds
+description: Installs dependencies, checks formatting, lints Markdown and code, type checks, builds, tests, and lints workflows
 
 runs:
     using: composite
@@ -34,3 +34,9 @@ runs:
         - name: Test
           shell: bash
           run: pnpm run test-ci
+
+        - name: Lint workflows
+          uses: raven-actions/actionlint@3d39aea434753780c3b3d4a1a31c854b4dbf49d7 # v2.2.0
+          with:
+              version: 1.7.12
+              pyflakes: false

CHANGELOG.md

@@ -6,6 +6,10 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ## [Unreleased]
 
+### Changed
+
+- `@commitlint/config-conventional` is now declared with a caret range instead of a tilde range. Consumers get its minor releases without waiting for a new release of this package.
+
 ## [1.0.0] - 2026-09-21
 
 ### Added

CONTRIBUTING.md

@@ -10,10 +10,7 @@ Open an [issue](https://github.com/dnd-mapp/config-commitlint/issues) to discuss
 
 ## Development setup
 
-The required tool versions are enforced through `devEngines` and `engineStrict`, so installing with other versions fails.
-
-- Node `24.21.0`
-- pnpm `12.5.1`
+The required Node and pnpm versions are set in `devEngines` in `package.json`. They are enforced through `engineStrict`, so installing with other versions fails.
 
 Install the dependencies with:
 
@@ -25,6 +22,8 @@ Dependency versions live in the catalogs in `pnpm-workspace.yaml`, which uses `c
 
 Newly published releases are held back for three days through `minimumReleaseAge`. You may need to wait before you can bump to a very recent version.
 
+Install [actionlint](https://github.com/rhysd/actionlint) to lint the workflows locally, for example with `brew install actionlint`. CI runs the version that `.github/actions/ci/action.yaml` pins.
+
 ## Git hooks
 
 [Lefthook](https://lefthook.dev/) installs the Git hooks when you run `pnpm install`. The hooks are defined in `lefthook.yaml`.
@@ -54,7 +53,7 @@ When you add or change a rule, update the "Rules" section of the README in the s
 
 Tests use Vitest and load the config with `@commitlint/load` and `@commitlint/lint`. Add a test for every rule that you add or change. Coverage must stay above the thresholds in `vitest.config.ts`.
 
-Check and format the repository with these commands. CI runs `format-check`, `lint-md`, `lint-ts`, `typecheck`, `test-ci`, and `build`. Run them yourself before you open a pull request.
+Check and format the repository with these commands. CI runs `format-check`, `lint-md`, `lint-ts`, `typecheck`, `test-ci`, `build`, and actionlint. Run them yourself before you open a pull request.
 
 ```bash
 pnpm run format-check
@@ -64,6 +63,7 @@ pnpm run lint-ts
 pnpm run typecheck
 pnpm run test-ci
 pnpm run build
+actionlint
 ```
 
 The `lint-md` script lints the Markdown files with markdownlint, and the `lint-ts` script lints the code with ESLint. Use `pnpm test` to run the tests in watch mode with the Vitest UI.
@@ -134,7 +134,8 @@ Write the description in the imperative mood, such as "add scope rule". Mark a b
 - Update the changelog and README in the same pull request.
 - Use a title that follows the commit convention.
 - If you have write access, turn on auto-merge once the pull request is open, with `gh pr merge <number> --auto --merge` or the "Enable auto-merge" button. It then merges as soon as it is approved and the checks pass.
-- If auto-merge is off, the author merges the pull request once it is approved and the checks pass. A maintainer merges pull requests opened by a bot or by a contributor without write access.
+- If auto-merge is off, the author merges the pull request once it is approved and the checks pass. A maintainer merges pull requests opened by a contributor without write access.
+- Renovate merges its own minor and patch pull requests once the checks pass. A maintainer approves a major update from Renovate and turns on auto-merge for it.
 - Update the branch when it falls behind `main`, because auto-merge waits until the branch is up to date. The update dismisses the approval, so the pull request needs a new review.
 
 ## License

pnpm-workspace.yaml

@@ -30,7 +30,7 @@ catalog:
 catalogs:
   commitlint:
     "@commitlint/cli": ~21.2.2
-    "@commitlint/config-conventional": ~21.2.2
+    "@commitlint/config-conventional": ^21.2.2
     "@commitlint/lint": ~21.2.2
     "@commitlint/load": ~21.2.2
     "@commitlint/types": ~21.2.0

renovate.json

@@ -0,0 +1,4 @@
+{
+    "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+    "extends": ["github>dnd-mapp/renovate-config#v1.0.0"]
+}