Bundle the open dependency bumps into one round #218
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "deps/bundle-version-bumps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bundles the open Renovate bump PRs into one branch, so the whole round gets one
review and one CI run. Supersedes #211, #213, #214, #215, #216 and #217. One
commit per lane, so
git logstill shows which bump came from where.Included
Held back on purpose
Two bumps in the round break something, and neither is caught by any gate we
run. Both were reproduced before deciding.
marked stays on
^18.0.7In 18.0.9 an empty nested blockquote swallows the paragraph that lazily
continues after it. Measured against 18.0.7, 18.0.8 and 18.0.9 side by side
with our own
{gfm: true, breaks: true}options:Same for
>>>and for> citaatfollowed by a bare>>. Every Mattermostmessage we render goes through
marked.parseinrenderSafeMarkdown, so thisis silent content loss in the card modal, the reading-list preview, the outbox
rows and the drafts page. It comes from the blockquote-continuation fix in
18.0.9; there is no upstream issue for it yet. The rest of the npm lane is
included.
@nldd/design-system stays on
^0.8.70, #212 stays open0.8.75 removed the four
--primitives-font-family-*-fallbacktokens.frontend/src/styles/tokens.css:46-47points the family chain at them onpurpose, because we may not use RijksSans (the licensing note is in that file).
Without those tokens the
var()reference is invalid at computed-value time,so
--primitives-font-family-sans-serifand the downstream--primitives-font-family-bodyboth compute to the empty string, which takesout the
body { font: ...; font-family: ... }rule inbase.csswholesale.Measured on the built bundle in Chromium:
font-familysystem-ui, sans-serifTimesfont-sizeline-heightTypecheck, eslint, vitest, the e2e suite and the build all pass on 0.8.77, so
nothing we run would have flagged it.
0.8.77 also carries two visual changes beyond that:
nldd-card's--components-card-box-shadowdefault went from level-1 tonone, andCardShell.vuerelies on that default for the resting state, so cards losetheir resting shadow; and the banner frame moved off
:hostinto a shadowwrapper, which double-pads
RetentionIntroBannerwhile giving the other sevenbanners the interior padding they currently lack. Those are design calls, not
dependency maintenance, so #212 is better handled on its own with the tokens
fix alongside it.
Verification
Every CI job was run locally against the final tree:
pre-commit run --all-files(pinned ruff 0.8.6, ty, gitleaks): pass-n auto, 100% coverage gate: 1610 passed, 100.00%ty check: passvue-tsctypecheck,eslint(0 errors), vitest: 570 passed in 77 filesvite build: passtest-release-scripts.sh: 20/20 after the changelog editcontainers/frontend,containers/backend)Two extra checks worth naming:
refresh-release-sha.shis best-effort and exits 0 on a fetch failure, so abumped version can ship with a stale pin. Both were matched against the
upstream checksum files: uv 0.12.1 against its
.sha256sidecar, trivy0.73.0 against
trivy_0.73.0_checksums.txt. Both match.npm ci(whichfails when
package.jsonandpackage-lock.jsondisagree) anduv lock --checkboth pass, and neither rewrote its lockfile.npm auditis unchanged from main: the same 6 pre-existing high-severity devtransitives (
@axe-core/cli->chromedriver->adm-zip,brace-expansion,ip-address,undici), with one moderate cleared.The ruff bump does not change any lint outcome: ruff 0.16.0 and 0.16.1 produce
identical output on this tree, and this PR touches no Python source.
17d410220d38e24ac92f