Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump next from 15.0.3 to 15.1.2 #494

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 6, 2025

Bumps next from 15.0.3 to 15.1.2.

Release notes

Sourced from next's releases.

v15.1.2

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Credits

Huge thanks to @​ztanner for helping!

v15.1.1

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Credits

Huge thanks to @​devjiwonchoi and @​ztanner for helping!

v15.1.1-canary.27

Core Changes

  • Update font data: #74572
  • Upgrade React from 3b009b4c-20250102 to 3ce77d55-20250106: #74557
  • [metadata] Change the array head to single node in flight data: #74299
  • [DevOverlay] Add Toolbar: #74555
  • restore deleted comment in next-app-loader: #74597
  • Turbopack dev: Remove client to server websocket ping event: #74584

Example Changes

  • chore(examples): update React in reproduction templates to stable 19: #74499

Misc Changes

  • chore(github): update issue_stale token to release bot token: #74575
  • chore(ci): Ensure all 6 shards are used equally in deploy tests: #74574
  • fix: force module format for virtual client-proxy file: #74162
  • [Turbopack] fix shadow-rs build caching: #74579

Credits

Huge thanks to @​samcx, @​nnnnoel, @​lubieowoce, @​huozhi, @​sokra, @​devjiwonchoi, and @​timneutkens for helping!

v15.1.1-canary.26

Core Changes

... (truncated)

Commits
  • df392a1 v15.1.2
  • 40c9424 Backport (v15): Update React from 7283a213-20241206 to 65e06cb7-20241218 (#74...
  • 4384c68 v15.1.1
  • d137863 run build_and_test workflow on backport branch
  • d27bb14 backport: fix(turbo): sassOptions silenceDeprecations was not overwritten wit...
  • 0c8187a Add NEXT_PRIVATE_SKIP_CANARY_CHECK env for bench job (#73763)
  • e83ab18 backport: refactor collectAppPageSegments (#73996)
  • ada25fc Designate as backport branch
  • dafcd43 v15.1.0
  • 2deb35d v15.0.4-canary.52
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 6, 2025
@samutoljamo-pareto
Copy link
Contributor

@Fuzzbender Next 15.1 forces React 19. We have still have a few deps that do not support React 19.
image

@Fuzzbender
Copy link
Contributor

Fuzzbender commented Feb 6, 2025

@Fuzzbender Next 15.1 forces React 19. We have still have a few deps that do not support React 19.

Can me update the deps as well? Or is it so that there is no new version for them that supports React19?

@samutoljamo-pareto
Copy link
Contributor

Looks like tests are still passing so those most likely either do not have R19 specific features or we do not use those parts. I think we could wait for a while, but looking at the packages, it might take some time...

@samutoljamo-pareto
Copy link
Contributor

@Fuzzbender Next 15.1 forces React 19. We have still have a few deps that do not support React 19.

Can me update the deps as well? Or is it so that there is no new version for them that supports React19?

They simply haven't been updated yet. They usually require small changes, but looks like e.g. use-resize-observer hasn't been updated in 2 years. Allthough there's a PR for the update which passes tests, it's not known if it gets published

@Fuzzbender
Copy link
Contributor

@Fuzzbender Next 15.1 forces React 19. We have still have a few deps that do not support React 19.

Can me update the deps as well? Or is it so that there is no new version for them that supports React19?

They simply haven't been updated yet. They usually require small changes, but looks like e.g. use-resize-observer hasn't been updated in 2 years. Allthough there's a PR for the update which passes tests, it's not known if it gets published

Why do we have swagger as react-ui?
Wouldn't it be easier to use non-react-ui for swagger? We wouldn't need to wait forever for changes to reach that.

@samutoljamo-pareto
Copy link
Contributor

@Fuzzbender Next 15.1 forces React 19. We have still have a few deps that do not support React 19.

Can me update the deps as well? Or is it so that there is no new version for them that supports React19?

They simply haven't been updated yet. They usually require small changes, but looks like e.g. use-resize-observer hasn't been updated in 2 years. Allthough there's a PR for the update which passes tests, it's not known if it gets published

Why do we have swagger as react-ui? Wouldn't it be easier to use non-react-ui for swagger? We wouldn't need to wait forever for changes to reach that.

NextJS uses React so if we want to easily render something, we must use react components. It makes them available by running cyberismo app and going to /api-doc

dependabot bot and others added 3 commits February 24, 2025 14:46
Bumps [next](https://github.com/vercel/next.js) from 15.0.3 to 15.1.2.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.0.3...v15.1.2)

---
updated-dependencies:
- dependency-name: next
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@samutoljamo-pareto samutoljamo-pareto force-pushed the dependabot/npm_and_yarn/next-15.1.2 branch from c5fc6ab to d77efbc Compare February 24, 2025 12:50
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 1, 2025

A newer version of next exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

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.

2 participants