Skip to content

chore(deps): batch lucide-react, install-action and @types/react-dom with one reseal - #209

Open
lamemustafa wants to merge 5 commits into
masterfrom
chore/dep-batch-204-206-207
Open

chore(deps): batch lucide-react, install-action and @types/react-dom with one reseal#209
lamemustafa wants to merge 5 commits into
masterfrom
chore/dep-batch-204-206-207

Conversation

@lamemustafa

Copy link
Copy Markdown
Owner

Batches the three remaining dependency bumps into a single reseal, superseding #204, #206 and #207.

bump from → to
lucide-react (frontend production) 1.33.0 → 1.34.0
taiki-e/install-action (CI) 2.86.4 → 2.87.0
@types/react-dom (frontend dev) 19.2.4 → 19.2.5

Why batched

Every reseal produces a new manifest digest, so the moment one dependency PR merges, every other one conflicts on compatibility-surface.json and compatibility-matrix.json. Merging five separately costs five full CI cycles and four rounds of conflict resolution; batching costs one. The original commits are preserved so attribution is intact.

The two steps dependabot cannot do

rehash-surface reported 3 changed pins — the workflow, package.json, and pnpm-lock.yaml. That last one is only caught because #208 pinned it; before this morning a lockfile change would have passed unrecorded.

lucide-react is a production frontend dependency, so it also drifts the locked frontend licence inventory. Unlike the Rust inventory there is no generator for it — license:generate:rust has no counterpart — so THIRD_PARTY_LICENSES.txt is updated by hand.

Verification

Surface at 135 pins, matrix agreeing, and an independent re-hash of all 135 showing zero mismatches. pnpm test 108, pnpm build clean, license:all matching 5 frontend and 380 Rust components, workspace 712, all-features 842 with 3 ignored, clippy and fmt clean.

The reseal was computed after rebasing onto current master, not before — resealing first and rebasing after would produce a valid digest over a stale tree, which is the exact hazard the tooling in #208 exists to prevent.

Follow-up

The dependency-update procedure is four steps, not three: reseal the surface, and regenerate the licence inventory — and the fourth step differs by ecosystem, with no generator at all on the frontend side. release-process.md documents these in separate sections; worth consolidating.

🤖 Generated with Claude Code

dependabot Bot and others added 5 commits August 31, 2026 19:01
Bumps the frontend-production group with 1 update: [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react).


Updates `lucide-react` from 1.33.0 to 1.34.0
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](https://github.com/lucide-icons/lucide/commits/1.34.0/packages/lucide-react)

---
updated-dependencies:
- dependency-name: lucide-react
  dependency-version: 1.34.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-production
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.86.4 to 2.87.0.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](taiki-e/install-action@a2a5f6e...37f7c57)

---
updated-dependencies:
- dependency-name: taiki-e/install-action
  dependency-version: 2.87.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps the frontend-development group with 1 update: [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom).


Updates `@types/react-dom` from 19.2.4 to 19.2.5
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom)

---
updated-dependencies:
- dependency-name: "@types/react-dom"
  dependency-version: 19.2.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-development
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-31T13:42:55.802905Z dc9f22e PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant