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

Update Next.js #2014

Merged
merged 1 commit into from
Sep 23, 2024
Merged

Update Next.js #2014

merged 1 commit into from
Sep 23, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 10, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-config-next (source) 13.5.6 -> 13.5.7 age adoption passing confidence
next (source) 14.2.8 -> 14.2.13 age adoption passing confidence
next-intl (source) 3.19.1 -> 3.19.4 age adoption passing confidence

Release Notes

vercel/next.js (eslint-config-next)

v13.5.7

Compare Source

vercel/next.js (next)

v14.2.13

Compare Source

v14.2.12

Compare Source

v14.2.11

Compare Source

v14.2.10

Compare Source

v14.2.9

Compare Source

amannn/next-intl (next-intl)

v3.19.4

Compare Source

Bug Fixes

v3.19.3

Compare Source

Bug Fixes

v3.19.2

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - "on the 2nd and 4th day instance on sunday after 9pm" in timezone America/New_York, 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.

Copy link

github-actions bot commented Jun 10, 2024

Coverage report for ./frontend

St.
Category Percentage Covered / Total
🟢 Statements 90.6% 790/872
🟡 Branches 71.79% 224/312
🟢 Functions 87.89% 167/190
🟢 Lines 91.27% 742/813

Test suite run success

178 tests passing in 54 suites.

Report generated by 🧪jest coverage report action from a4fa641

@renovate renovate bot force-pushed the renovate/next.js branch 2 times, most recently from a2b6f43 to 0aaff85 Compare June 12, 2024 01:20
@renovate renovate bot force-pushed the renovate/next.js branch 2 times, most recently from 0fdb6c8 to 6abf8fd Compare June 24, 2024 13:53
@renovate renovate bot force-pushed the renovate/next.js branch 6 times, most recently from fa2fd59 to bfd1c26 Compare July 15, 2024 15:01
@renovate renovate bot force-pushed the renovate/next.js branch 2 times, most recently from af7e537 to 29c0b99 Compare August 20, 2024 15:12
@renovate renovate bot force-pushed the renovate/next.js branch 5 times, most recently from bcb073a to 7f8b24f Compare August 28, 2024 17:17
@renovate renovate bot force-pushed the renovate/next.js branch 3 times, most recently from 9a9380b to 0bd892c Compare September 5, 2024 14:37
@renovate renovate bot force-pushed the renovate/next.js branch 3 times, most recently from 0d68581 to d30933c Compare September 12, 2024 19:58
@renovate renovate bot force-pushed the renovate/next.js branch 7 times, most recently from e21c375 to dc58d4f Compare September 19, 2024 16:25
Copy link
Collaborator

@doug-s-nava doug-s-nava left a comment

Choose a reason for hiding this comment

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

Notes from my review:

  • Started up locally on this branch and the app seems to be functioning as expected as far as loading and navigation between static pages
  • Ran linter locally and it ran with no errors (beyond a note that the Typescript version on the project is too new to be fully supported by typescript-eslint)
  • The search page seems broken on this branch the same way it is on main, so no red flags there
  • Since it looks like I need to get the API running to test the opportunities page, I have not been able to do that yet, but working on it and will report back on results when I have them
  • When running an npm install on this branch using node 20.17 I got a lot of changes to the package lock related to using a newer version on npm. Since the engines in the package.json specify >20 I'm not sure what to make of this. Tried to do an install with node 10 to test behavior there but it errored out on an optional chain.
  • During the install I also get errors related to three packages, though these errors also appear when running the install on main:

So that's what I'm seeing. Nothing seems like a blocker other than maybe the question of the lockfile version / npm version, but not sure what exactly is expected here so I'll hold off on approving

@doug-s-nava
Copy link
Collaborator

After spinning up the API server, can confirm that the search and opportunity pages function as expected.

@renovate renovate bot force-pushed the renovate/next.js branch 4 times, most recently from 1f523e1 to 27a9521 Compare September 20, 2024 04:02
@renovate renovate bot force-pushed the renovate/next.js branch 2 times, most recently from cc90f69 to cb93b3a Compare September 20, 2024 16:09
@acouch
Copy link
Collaborator

acouch commented Sep 23, 2024

@doug-s-nava Thanks for the review. Please merge!

During the install I also get errors related to three packages, though these errors also appear when running the install on main

Can you create an issue? Thanks!

@doug-s-nava doug-s-nava merged commit f0d8621 into main Sep 23, 2024
12 checks passed
@doug-s-nava doug-s-nava deleted the renovate/next.js branch September 23, 2024 15:36
@doug-s-nava
Copy link
Collaborator

created #2195 and #2194 as follow ups

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

Successfully merging this pull request may close these issues.

2 participants