Repository navigation
chore(deps): safe updates, and Renovate opens PRs again - #10
Merged
Merged
Conversation
…sh lockfile What Renovate had waiting on its dashboard, without the majors: - maplibre-gl ^6.16.0 (the update of #9) - @geomatico/maplibre-cog-protocol ^0.10.0. Transparency now follows GDAL semantics; the three COG demos render the same as on map0.net (0.9.3). - hyparquet ^1.31.5; lit ^3.3.3 in the configurator (already locked at 3.3.3) - dev: ace-builds ^1.45.2, node-html-parser ^9.0.5, vite ^6.4.5 - actions/upload-artifact v7. The step passes only name, path and if-no-files-found, and v4 still ran on Node 20. - pnpm 12.16.1. 12.16.0 fixes two security issues (zstd decompression, signing), and 12.16.1 stops `pnpm pack` from shipping a file that `files` excludes by name. It is two days old, under the three-day release age; taken anyway because of those fixes. - lockfile regenerated (the monthly lockfile maintenance): rollup 4.66, postcss 8.5.32, maplibre-gl-style-spec 26.5, inquirer and a few other transitive patches Left out: TypeScript 7, Vite 8, Vitest 5, @types/node 26, Node 26.
No Renovate PR opened between 2026-10-19 and 2026-10-29. prCreation "not-pending" waits for a check on the branch. CI did not run on renovate/** pushes, and Renovate does not count its own renovate/stability-days, so each branch waited prNotPendingHours (25 h). By then the "before 6am on monday" window was over, and the branch went back to "Awaiting Schedule". Those five branches plus #9 filled the branch limit (it inherits prConcurrentLimit 5), so every other update showed up as "Rate-Limited". - CI runs on every push to renovate/** and skips the pull_request run of those PRs. - schedule: the whole Monday; lockfile maintenance the whole first day of the month; prHourlyLimit 0. - majors wait for a tick on the Dependency Dashboard (dependencyDashboardApproval), so they no longer hold branch slots. - node: bump joins minor, patch and pin. `24` -> `24.22.1` had come back after #6 was closed. - engines are not updated at all. @types/node stays below 23, matching map0-check's engines.node >=22. docs/09 §10 has the reasoning.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://brave-mud-0c9fbf503-10.westeurope.7.azurestaticapps.net |
None of what Vitest 5 removes is used here. There is no `sequential` option, the `.each` titles use `%s`/`%j` and not `$` variables, and the only imports are `vitest` and `vitest/config`. Vitest 5 needs Vite 6.4, which is what we run. 377 tests pass with no warnings.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://brave-mud-0c9fbf503-10.westeurope.7.azurestaticapps.net |
pergerch
added a commit
that referenced
this pull request
Oct 29, 2026
After #10 the manual run still offered node-version 24 -> 24.22.1. The `bump` explanation in #10 was wrong. Renovate looks up actions/setup-node's node-version with depName `node` but packageName `actions/node-versions` (GitHub releases), so `matchPackageNames: ["node"]` never matched it. `matchDepNames` does. docs/09 §10 now gives the real reason. It also notes that branches that existed before the approval rule skip it: TypeScript 7 and Vite 8 kept their branches and were deleted by hand.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three commits: the safe updates from the Dependency Dashboard (#5), the config fix that stops Renovate getting stuck again, and Vitest 5. Supersedes #9.
pnpm packfilesfix in 12.16.1; two days old, taken on purposesequential,$titles, old entry points), needs Vite 6.4Left out: TypeScript 7 (no classic compiler API, which
scripts/build-types.mjsand dts-bundle-generator need), Vite 8 (Rolldown, its own PR), @types/node 26, Node 26.Why Renovate stalled (no PR since 2026-10-19), and what changes:
docs/09 §10 has the reasoning.
Evidence
After: local run of every CI step on this branch:
pnpm typecheck✓pnpm test: 377/377, on Vitest 4.1.12 and again on 5.0.5 (no warnings)pnpm build✓pnpm smoke: 80/80pnpm visual: 12/12 scenes matchpnpm size: page load 35.3 KB of 40 KBpnpm build:site✓demos/cog.html(RGB imagery, terrain + hillshade, classes with the semi-transparent "unsealed" class) look the same locally as on map0.net (0.9.3), with no console errors.renovate-config-validator --strict: "Config validated successfully". Under Node 26 it logs an RE2 load error (prebuilt for Node 24) and falls back to RegExp; the config has no regex patterns, so that fallback changes nothing here.Merge Danger
Door: two-way
Blast Radius: bundle
maplibre-gl 6.16 and the COG protocol 0.10 ship in
map0-viewer. After pulling,pnpm installswitches to pnpm 12.16.1. Renovate closes its now-obsolete branches on its next run.🤖 Generated with Claude Code