Skip to content

deps(npm): bump the npm-minor-patch group across 1 directory with 2 updates#210

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-minor-patch-4790852394
Open

deps(npm): bump the npm-minor-patch group across 1 directory with 2 updates#210
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-minor-patch-4790852394

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 15, 2026

Copy link
Copy Markdown
Contributor

Bumps the npm-minor-patch group with 2 updates in the / directory: next and @remotion/renderer.

Updates next from 16.2.7 to 16.2.10

Release notes

Sourced from next's releases.

v16.2.10

Contains no changes except publishing @next/swc-wasm-web which was accidentally not published since 16.2.4.

v16.2.9

Empty release to ensure next@latest points at a stable release. Next.js only allows publishing with Trusted Publishing enabled. In order to fix NPM dist-tags, we have to release a new version. Updating dist-tags is not possible with Trusted Publishing.

v16.2.8

Release with no changes in an attempt to fix next@latest pointing at a prerelease version.

Commits

Updates @remotion/renderer from 4.0.471 to 4.0.485

Release notes

Sourced from @​remotion/renderer's releases.

v4.0.485

What's Changed

Docs

Internal

Full Changelog: remotion-dev/remotion@v4.0.484...v4.0.485

v4.0.484

What's Changed

... (truncated)

Commits

@dependabot @github

dependabot Bot commented on behalf of github Jun 15, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, javascript. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@vercel

vercel Bot commented Jun 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
all-source-admin Ready Ready Preview, Comment Jul 6, 2026 6:58pm
all-source-web Ready Ready Preview, Comment Jul 6, 2026 6:58pm

Comment on lines 22 to 27
"@remotion/bundler": "^4.0.450",
"@remotion/cli": "^4.0.450",
"@remotion/renderer": "4.0.471",
"@remotion/renderer": "4.0.481",
"react": "^19.1.0",
"react-dom": "^19.1.0",
"remotion": "^4.0.450"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Remotion package version mismatch@remotion/renderer is now pinned at 4.0.481 while @remotion/bundler, @remotion/cli, and remotion are constrained to ^4.0.450. Remotion explicitly requires all packages to be on the exact same version. If any of the ^4.0.450 packages resolve or later update to a different version than 4.0.481, the renderer will be on a mismatched version and rendering will likely fail. Either pin all Remotion packages to the same exact version, or align the caret ranges so they all track together.

…pdates

Bumps the npm-minor-patch group with 2 updates in the / directory: [next](https://github.com/vercel/next.js) and [@remotion/renderer](https://github.com/remotion-dev/remotion).


Updates `next` from 16.2.7 to 16.2.10
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.2.7...v16.2.10)

Updates `@remotion/renderer` from 4.0.471 to 4.0.485
- [Release notes](https://github.com/remotion-dev/remotion/releases)
- [Commits](remotion-dev/remotion@v4.0.471...v4.0.485)

---
updated-dependencies:
- dependency-name: "@remotion/renderer"
  dependency-version: 4.0.477
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: next
  dependency-version: 16.2.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
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.

0 participants