chore(version): Upgrade next from 14.0.4 to 14.1.0

[rajdip-b]

User description

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade next from 14.0.4 to 14.1.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 69 versions ahead of your current version.
• The recommended version was released 23 days ago, on 2024-01-18.

Release notes

Package name: next

• 14.1.0 - 2024-01-18
  Read more
• 14.0.5-canary.68 - 2024-01-18
  

  Core Changes

  • Enable missing suspense bailout by default: #60840

  Credits

  Huge thanks to @ huozhi for helping!

• 14.0.5-canary.67 - 2024-01-18
  

  Core Changes

  • fix(ts): auto-complete next/headers: #60817
  • Remove the warning for build worker when custom webpack present: #60820
  • chore(deps): update browserslist and caniuse-lite: #60827
  • feat: support custom image loaders in turbopack: #60736
  • Ensure request specific caches for revalidate are reset: #60810
  • Add metrics names for unstable_cache: #60802
  • Fix: respect init.cache if fetch input is request instance: #60821
  • Revert "Fix: Throw an error for empty array return in generateStaticParams with output:export": #60831
  • turbopack: rename custom cache handler configs: #60828
  • dx: warn the deprecated cache configs are used: #60836

  Documentation Changes

  • add authentication docs page: #60388
  • chore(docs): fix example documentation for Art Direction: #60823
  • docs: add build worker optout error back with upgrade advice: #60826
  • Docs: Use JS comment for MDX: #60825
  • Fix error from the auth docs.: #60829

  Credits

  Huge thanks to @ balazsorban44, @ StephDietz, @ huozhi, @ styfle, @ delbaoliveira, @ ForsakenHarmony, @ leerob, and @ ijjk for helping!

• 14.0.5-canary.66 - 2024-01-18
  

  Core Changes

  • feat: stabilize unstable_getImgProps() => getImageProps(): #60739
  • Fix Server Actions compiler bug: #60794
  • Dev Server: Preserve globals overwrites in the initialization hook: #60796
  • add missing function call to normalize-catchall-routes test case: #60777
  • Use snapshots for component-stack tests: #60768
  • Support next/og usage in ESM nextjs app: #60818

  Misc Changes

  • Update ReactRefreshRegression test snapshot for Turbopack: #60767

  Credits

  Huge thanks to @ styfle, @ shuding, @ dvoytenko, @ williamli, @ timneutkens, and @ huozhi for helping!

• 14.0.5-canary.65 - 2024-01-17
  

  Core Changes

  • Fix locale domain public files check: #60749
  • Stabilize custom cache handlers and changing memory size.: #57953

  Credits

  Huge thanks to @ ijjk and @ leerob for helping!

• 14.0.5-canary.64 - 2024-01-17
  

  Core Changes

  • fix layout segment key to match up with manifest: #60783

  Misc Changes

  • Fix tests exit race condition: #60757

  Credits

  Huge thanks to @ ijjk and @ sokra for helping!

• 14.0.5-canary.63 - 2024-01-17
  

  Core Changes

  • Skip postcss config location resolving in node_modules: #60697
  • apply page transforms only on pages: #60779

  Credits

  Huge thanks to @ timneutkens and @ sokra for helping!

• 14.0.5-canary.62 - 2024-01-17
  

  Core Changes

  • Reapply "feat(app-router): introduce experimental.missingSuspenseWithCSRBailout flag" (#60508): #60751

  Credits

  Huge thanks to @ sokra for helping!

• 14.0.5-canary.61 - 2024-01-17
  Read more
• 14.0.5-canary.60 - 2024-01-16
  Read more
• 14.0.5-canary.59 - 2024-01-15
• 14.0.5-canary.58 - 2024-01-14
• 14.0.5-canary.57 - 2024-01-14
• 14.0.5-canary.56 - 2024-01-13
• 14.0.5-canary.55 - 2024-01-12
• 14.0.5-canary.54 - 2024-01-12
• 14.0.5-canary.53 - 2024-01-11
• 14.0.5-canary.52 - 2024-01-11
• 14.0.5-canary.51 - 2024-01-11
• 14.0.5-canary.50 - 2024-01-10
• 14.0.5-canary.49 - 2024-01-10
• 14.0.5-canary.48 - 2024-01-10
• 14.0.5-canary.47 - 2024-01-10
• 14.0.5-canary.46 - 2024-01-09
• 14.0.5-canary.45 - 2024-01-08
• 14.0.5-canary.44 - 2024-01-08
• 14.0.5-canary.43 - 2024-01-07
• 14.0.5-canary.42 - 2024-01-06
• 14.0.5-canary.41 - 2024-01-05
• 14.0.5-canary.40 - 2024-01-05
• 14.0.5-canary.39 - 2024-01-04
• 14.0.5-canary.38 - 2024-01-04
• 14.0.5-canary.37 - 2024-01-04
• 14.0.5-canary.36 - 2024-01-03
• 14.0.5-canary.35 - 2024-01-02
• 14.0.5-canary.34 - 2024-01-01
• 14.0.5-canary.33 - 2023-12-31
• 14.0.5-canary.32 - 2023-12-30
• 14.0.5-canary.31 - 2023-12-29
• 14.0.5-canary.30 - 2023-12-29
• 14.0.5-canary.29 - 2023-12-27
• 14.0.5-canary.28 - 2023-12-26
• 14.0.5-canary.27 - 2023-12-25
• 14.0.5-canary.26 - 2023-12-24
• 14.0.5-canary.25 - 2023-12-23
• 14.0.5-canary.24 - 2023-12-22
• 14.0.5-canary.23 - 2023-12-21
• 14.0.5-canary.22 - 2023-12-20
• 14.0.5-canary.21 - 2023-12-20
• 14.0.5-canary.20 - 2023-12-20
• 14.0.5-canary.19 - 2023-12-19
• 14.0.5-canary.18 - 2023-12-18
• 14.0.5-canary.17 - 2023-12-17
• 14.0.5-canary.16 - 2023-12-16
• 14.0.5-canary.14 - 2023-12-15
• 14.0.5-canary.13 - 2023-12-14
• 14.0.5-canary.12 - 2023-12-13
• 14.0.5-canary.11 - 2023-12-13
• 14.0.5-canary.10 - 2023-12-13
• 14.0.5-canary.9 - 2023-12-13
• 14.0.5-canary.8 - 2023-12-12
• 14.0.5-canary.7 - 2023-12-11
• 14.0.5-canary.6 - 2023-12-11
• 14.0.5-canary.5 - 2023-12-09
• 14.0.5-canary.4 - 2023-12-08
• 14.0.5-canary.3 - 2023-12-08
• 14.0.5-canary.2 - 2023-12-08
• 14.0.5-canary.1 - 2023-12-08
• 14.0.5-canary.0 - 2023-12-07
• 14.0.4 - 2023-12-07

from next GitHub release notes

Commit messages

Package name: next

• 16e7a5b v14.1.0
• 8a3881f Update labeler.json (#60843)
• 1b255a6 v14.0.5-canary.68
• 02c2f11 Enable missing suspense bailout by default (#60840)
• 2096dfa v14.0.5-canary.67
• b8d8e6e dx: warn the deprecated cache configs are used (#60836)
• c192f4e turbopack: rename custom cache handler configs (#60828)
• 2227ae5 Revert "Fix: Throw an error for empty array return in `generateStaticParams` with `output:export`" (#60831)
• b7f5107 Fix: respect init.cache if fetch input is request instance (#60821)
• 752c15e Add metrics names for unstable_cache (#60802)
• e733853 Ensure request specific caches for revalidate are reset (#60810)
• ecbc36c Fix error from the auth docs. (#60829)
• c247347 feat: support custom image loaders in turbopack (#60736)
• cb71d80 chore(deps): update `browserslist` and `caniuse-lite` (#60827)
• 54f73a2 Docs: Use JS comment for MDX (#60825)
• d450ff7 docs: add build worker optout error back with upgrade advice (#60826)
• afcafcd chore(docs): fix example documentation for Art Direction (#60823)
• 7472cef Remove the warning for build worker when custom webpack present (#60820)
• 65fce8a add authentication docs page (#60388)
• b14c1eb fix(ts): auto-complete `next/headers` (#60817)
• 8179e70 v14.0.5-canary.66
• e0399ca Support next/og usage in ESM nextjs app (#60818)
• 299d145 Use snapshots for component-stack tests (#60768)
• 486567d Update ReactRefreshRegression test snapshot for Turbopack (#60767)

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

---

Type

enhancement

---

Description

• Upgraded Next.js from 14.0.4 to 14.1.0 to incorporate the latest features and improvements.

---

Changes walkthrough

	Relevant files
Dependencies	package.json Upgrade Next.js to 14.1.0                                                                            package.json Upgraded next from version 14.0.4 to 14.1.0. +1/-1

---

✨ Usage guide:

---

Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.

When commenting, to edit configurations related to the describe tool (pr_description section), use the following template:

/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:

[pr_description]
some_config1=...
some_config2=...

Enabling\disabling automation When you first install the app, the default mode for the describe tool is: pr_commands = ["/describe --pr_description.add_original_user_description=true" "--pr_description.keep_original_user_title=true", ...] meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description. Markers are an alternative way to control the generated description, to give maximal control to the user. If you set: pr_commands = ["/describe --pr_description.use_description_markers=true", ...] the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following: type: the PR type. summary: the PR summary. walkthrough: the PR walkthrough. Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

Custom labels The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other]. If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases. Examples for custom labels: Main topic:performance - pr_agent:The main topic of this PR is performance New endpoint - pr_agent:A new endpoint was added in this PR SQL query - pr_agent:A new SQL query was added in this PR Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile ... The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases. Note that Labels are not mutually exclusive, so you can add multiple label categories. Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

Inline File Walkthrough 💎 For enhanced user experience, the describe tool can add file summaries directly to the "Files changed" tab in the PR page. This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs). To enable inline file summary, set pr_description.inline_file_summary in the configuration file, possible values are: 'table': File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab. true: A collapsable file comment with changes title and a changes summary for each file in the PR. false (default): File changes walkthrough will be added only to the "Conversation" tab.

Utilizing extra instructions The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description. Examples for extra instructions: [pr_description] extra_instructions=""" - The PR title should be in the format: '<PR type>: <title>' - The title should be short and concise (up to 10 words) - ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the describe usage page for a comprehensive guide on using this tool.

[codiumai-pr-agent-free]

PR Description updated to latest commit (a390e6e)

[codiumai-pr-agent-free]

PR Review

(review updated until commit 79f476c)

PR feedback
⏱️ Estimated effort to review [1-5]	1, because the PR involves a straightforward version upgrade of the "next" package from 14.0.4 to 14.1.0. The change is limited to a single line in the package.json file, which simplifies the review process.
🧪 Relevant tests	No
🔍 Possible issues	Dependency upgrades can sometimes introduce breaking changes or new bugs, especially when jumping multiple versions. It's important to thoroughly test the application to ensure that the upgrade does not break existing functionality.
🔒 Security concerns	No

Code feedback:

---

relevant file	package.json
suggestion	Consider pinning the version of "next" to "14.1.0" instead of using the caret (^) version range. This can help ensure that all developers and the production environment are using the exact same version, reducing the chances of encountering unexpected behavior due to version mismatches. [important]
relevant line	"next": "^14.1.0",

---

---

✨ Usage guide:

---

Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

Utilizing extra instructions The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize. Examples for extra instructions: [pr_reviewer] # /review # extra_instructions=""" In the 'possible issues' section, emphasize the following: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

How to enable\disable automation When you first install PR-Agent app, the default mode for the review tool is: pr_commands = ["/review", ...] meaning the review tool will run automatically on every PR, with the default configuration. Edit this field to enable/disable the tool, or to change the used configurations

Auto-labels The review tool can auto-generate two specific types of labels for a PR: a possible security issue label, that detects possible security issues (enable_review_labels_security flag) a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

Extra sub-tools The review tool provides a collection of possible feedbacks about a PR. It is recommended to review the possible options, and choose the ones relevant for your use case. Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example: require_score_review, require_soc2_ticket, and more.

Auto-approve PRs By invoking: /review auto_approve The tool will automatically approve the PR, and add a comment with the approval. To ensure safety, the auto-approval feature is disabled by default. To enable auto-approval, you need to actively set in a pre-defined configuration file the following: [pr_reviewer] enable_auto_approval = true (this specific flag cannot be set with a command line argument, only in the configuration file, committed to the repository) You can also enable auto-approval only if the PR meets certain requirements, such as that the estimated_review_effort is equal or below a certain threshold, by adjusting the flag: [pr_reviewer] maximal_review_effort = 5

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit a390e6e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 2 targets

• nx run web:test
• nx run web:lint

---

Sent with 💌 from NxCloud.

[codiumai-pr-agent-free]

PR Code Suggestions

	Suggestions
best practice	Use a caret version specifier for the "next" package to automatically receive updates. Consider using a caret (^) version specifier for the "next" package to automatically upgrade to newer minor versions. This can help ensure that you receive important updates and bug fixes. For example, use "^14.1.0" instead of "14.1.0". package.json [196] -"next": "14.1.0", +"next": "^14.1.0",

---

✨ Usage guide:

---

Overview:
The improve tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.
When commenting, to edit configurations related to the improve tool (pr_code_suggestions section), use the following template:

/improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=...

With a configuration file, use the following template:

[pr_code_suggestions]
some_config1=...
some_config2=...

Enabling\disabling automation When you first install the app, the default mode for the improve tool is: pr_commands = ["/improve --pr_code_suggestions.summarize=true", ...] meaning the improve tool will run automatically on every PR, with summarization enabled. Delete this line to disable the tool from running automatically.

Utilizing extra instructions Extra instructions are very important for the improve tool, since they enable to guide the model to suggestions that are more relevant to the specific needs of the project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify relevant aspects that you want the model to focus on. Examples for extra instructions: [pr_code_suggestions] # /improve # extra_instructions=""" Emphasize the following aspects: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

A note on code suggestions quality While the current AI for code is getting better and better (GPT-4), it's not flawless. Not all the suggestions will be perfect, and a user should not accept all of them automatically. Suggestions are not meant to be simplistic. Instead, they aim to give deep feedback and raise questions, ideas and thoughts to the user, who can then use his judgment, experience, and understanding of the code base. Recommended to use the 'extra_instructions' field to guide the model to suggestions that are more relevant to the specific needs of the project, or use the custom suggestions 💎 tool With large PRs, best quality will be obtained by using 'improve --extended' mode.

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the improve usage page for a more comprehensive guide on using this tool.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[rajdip-b]

/review

[codiumai-pr-agent-free]

Persistent review updated to latest commit 79f476c

[rajdip-b]

🎉 This PR is included in version 1.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀