Skip to content

chore(deps): pin dependencies - #7

Merged
bradwindy merged 1 commit into
mainfrom
renovate/react
Jul 9, 2026
Merged

bradwindy merged 1 commit into
mainfrom
renovate/react

Conversation

@renovate

@renovate renovate Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change Age Confidence
@types/react (source) devDependencies pin ^19.0.0 → 19.2.15 age confidence
@types/react-dom (source) devDependencies pin ^19.0.0 → 19.2.3 age confidence
react (source) dependencies patch 19.2.6 → 19.2.7 age confidence
react-dom (source) dependencies patch 19.2.6 → 19.2.7 age confidence

⚠️ Renovate's pin functionality does not currently wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.


Release Notes

facebook/react (react)

v19.2.7: 19.2.7 (June 1st, 2026)

Compare Source

React Server Components

Configuration

📅 Schedule: (in timezone Pacific/Auckland)

  • Branch creation
    • "before 9am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Jul 9, 2026
@renovate
renovate Bot force-pushed the renovate/react branch 7 times, most recently from bcb0137 to 71fcb35 Compare July 9, 2026 03:26
@renovate
renovate Bot force-pushed the renovate/react branch from 71fcb35 to 75b386e Compare July 9, 2026 03:27
@bradwindy
bradwindy merged commit 672c830 into main Jul 9, 2026
3 checks passed
@bradwindy
bradwindy deleted the renovate/react branch July 9, 2026 03:27
bradwindy added a commit that referenced this pull request Jul 9, 2026
…nstant-time auth, input validation (#31)

* fix: address code-review findings (races, SSRF, constant-time auth, input validation)

Web app (collection-reviewer-web):
- Route progress writes through the existing write mutex so /api/sync and
  /api/progress no longer race and clobber the progress index (#1).
- Give atomicWrite a unique per-write temp name + failure cleanup, so
  concurrent writers can't collide on a shared *.tmp and leave a partial
  write / ENOENT crash (#4).
- Validate and clamp the /api/images count param (parseImageCount): a
  non-numeric value no longer silently yields 0 images, and a huge value
  can't spawn unbounded concurrent lambda fetches (#2).
- Clamp a stale/out-of-range progress index in mergeCollections
  (remapProgress) instead of silently resetting the reviewer to 0 (#5).
- Guard await request.json() in the decision + progress routes so a
  malformed body returns 400 instead of a raw 500 (#7).

Swift API Lambda:
- constantTimeEquals now reduces each operand to a fixed 32-byte SHA-256
  digest before the XOR compare, removing the secret-length timing leak
  from the previous early length-mismatch return (#6).

Converter Lambda:
- Enforce an http/https scheme allowlist, re-validate every redirect target
  against internal IP ranges (IMDS / loopback / RFC1918) while still
  permitting the legitimate public S3 redirect, and return generic error
  bodies instead of echoing raw exceptions (#3).

Tests: add Vitest plus web unit tests (atomicWrite, remapProgress,
parseImageCount, progress mutex, JSON-body guards); extend
AuthorizedConsumerTests with unequal-length cases; extend the converter
pytest suite with scheme/redirect SSRF and error-opacity coverage.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019YqwmybDadEYqqfDMrHvxs

* fix: reject null/primitive JSON bodies in decision + progress routes

CodeRabbit review: request.json() returns null (or a bare primitive) without
throwing for a body like "null" or "42"; the subsequent destructuring then threw
a TypeError outside the try/catch, yielding a 500 instead of the intended 400.
Add an explicit non-null-object guard before destructuring in both write routes,
and cover it with valid-JSON "null" body tests.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019YqwmybDadEYqqfDMrHvxs

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant