@leaflink/dom-testing-utils 0.0.0-PR-201--cd9961d → 0.0.0-PR-207--5f7838b

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +34 -0
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -51,6 +51,40 @@ Releases are fully automated using [semantic-release](https://github.com/semanti
51
51
 
52
52
  For detailed commit conventions and manual release instructions, see [CONTRIBUTING.md](.github/CONTRIBUTING.md#semantic-release).
53
53
 
54
+ ## Dependency updates
55
+
56
+ Dependency updates are handled by self-hosted [Renovate](https://docs.renovatebot.com/), invoked from `.github/workflows/renovate.yml` using a PAT (`RENOVATE_TOKEN`) issued from the `leaflink-automation` account. Configuration lives in [`.github/renovate.json5`](.github/renovate.json5). Tracking ticket: [MKPL-1055](https://leaflink.atlassian.net/browse/MKPL-1055).
57
+
58
+ ### Schedule
59
+
60
+ - Workflow cron wakes Renovate hourly.
61
+ - Renovate only opens PRs and merges between **1am–5am America/New_York**, every day.
62
+ - A new release must be **≥ 10 days old** (`minimumReleaseAge`) before Renovate will propose it — buffer against compromised/withdrawn publishes.
63
+ - Merging is done by Renovate itself (`platformAutomerge: false`), not GitHub's native auto-merge — so a PR that goes green merges on the next hourly wake inside the schedule window.
64
+
65
+ ### Update groups and auto-merge policy
66
+
67
+ | Source | Update type | PR shape | Auto-merge |
68
+ |---|---|---|---|
69
+ | `devDependencies` | any | grouped as one PR (`chore(deps-dev): update dev dependencies`) | ✅ |
70
+ | `dependencies` / `peerDependencies` | **patch** | individual PR (`chore(deps): ...`) | ✅ |
71
+ | `dependencies` / `peerDependencies` | **minor / major** | individual PR (`chore(deps): ...`) | ❌ awaits review |
72
+ | `github-actions` | patch / minor / digest / pin | individual PR | ✅ |
73
+ | `github-actions` | major | individual PR | ❌ awaits review |
74
+ | Lockfile maintenance (transitive refresh of `pnpm-lock.yaml`) | weekly | `Refresh ... (chore(deps-dev))` | ✅ |
75
+
76
+ Renovate PR bodies all link back to MKPL-1055 via `prBodyNotes`.
77
+
78
+ ### How auto-merge interacts with branch protection
79
+
80
+ `main` requires `quality-checks` + `release` status checks and a CODEOWNERS review. The Renovate PAT is issued from `leaflink-automation`, which is in `main`'s `bypass_pull_request_allowances` — bypass covers the review requirement only; required status checks still gate every merge.
81
+
82
+ ### Where to look
83
+
84
+ - **Dependency Dashboard issue** (auto-created by Renovate, label `dependencies`) — single source of truth for what Renovate sees, what it skipped, and why.
85
+ - **Workflow runs** for `Renovate` in the Actions tab — `workflow_dispatch` with `logLevel: debug` to debug.
86
+ - **`config:recommended`** is the base preset; any unspecified behavior comes from there.
87
+
54
88
  ## Usage
55
89
 
56
90
  In your test files you can import utility functions.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@leaflink/dom-testing-utils",
3
- "version": "0.0.0-PR-201--cd9961d",
3
+ "version": "0.0.0-PR-207--5f7838b",
4
4
  "description": "Frontend DOM testing utilities",
5
5
  "packageManager": "pnpm@10.12.2",
6
6
  "engines": {
@@ -49,7 +49,7 @@
49
49
  "@vitest/coverage-v8": "^4.1.6",
50
50
  "commitlint": "^21.0.0",
51
51
  "conventional-changelog-conventionalcommits": "^9.3.0",
52
- "eslint": "^10.4.0",
52
+ "eslint": "^9.39.2",
53
53
  "jsdom": "^29.1.1",
54
54
  "semantic-release": "^25.0.3",
55
55
  "stylelint": "^17.11.0",