72f5429fe0
Docs IA 2.0: Add i18n guides ( #79391 )
...
Closes:
https://linear.app/vercel/issue/DOC-4682/guide-internationalization-i18n
Redirects: https://github.com/vercel/front/pull/45963
2025-05-21 15:43:02 +01:00
f8bbb5e0ed
Docs IA 2.0: Review fetching page and move examples ( #79200 )
...
Part of:
https://linear.app/vercel/issue/DOC-4639/ia-20-migrate-bya-pages
No redirects needed yet as the page hasn't been deleted.
2025-05-21 15:38:11 +01:00
f4406d8c58
docs: htmlLimitedBots config value should be a RegExp ( #79454 )
...
Closes: https://linear.app/vercel/issue/DOC-4697/htmllimitedbots-value
Also fixes `Behavior` sub heading
2025-05-21 15:27:41 +01:00
f6081d019c
Docs IA 2.0: Move ISR page to guides ( #79283 )
...
Closes: https://linear.app/vercel/issue/DOC-4670/isr
Redirects: https://github.com/vercel/front/pull/45793
2025-05-21 08:34:00 +01:00
e675d2ba99
docs: fix spacing in installation instructions ( #79257 )
...
This PR fixes a minor spacing issue in the "Run the development server"
section of the installation guide.
No functionality is affected.
---------
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2025-05-20 17:59:53 +00:00
5d2082ba36
fix(doc): fix typo ( #79369 )
...
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
### Adding or Updating Examples
- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas )
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs )
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
``croppint`` is a typo for ``cropping``, could be misleading
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2025-05-19 10:31:21 -07:00
e9e30ee743
docs: Fix flag for taint ( #79370 )
...
Closes:
https://linear.app/vercel/issue/DOC-4668/document-the-experimentaltaint-option-in-nextconfigts
Flag value was incorrect.
2025-05-19 09:35:09 -05:00
0e784439f9
docs: --verbose option in dev mode is not yet supported ( #79366 )
...
Closes:
https://linear.app/vercel/issue/DOC-4677/remove-reference-to-next-dev-verbose
Fixes: https://github.com/vercel/next.js/issues/79337
For now, `--verbose` is not supported for `next dev`.
---------
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2025-05-19 07:47:28 -05:00
aa96aa9615
Docs: Experimental taint option in next.config.js ( #79293 )
...
Closes:
https://linear.app/vercel/issue/DOC-4668/document-the-experimentaltaint-option-in-nextconfigts
- Documents activation of taint APIs within Next.js
- Documents basic usage of the taint APIs
---------
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2025-05-19 13:06:15 +01:00
86ea212c9b
Add missing / to deploying link
2025-05-18 20:34:12 +02:00
9832e844e0
docs: Fix syntax highlighting, add missing js code blocks ( #79246 )
2025-05-15 14:36:57 +00:00
b15817b46c
Docs IA 2.0: Delete rendering section ( #79244 )
...
All pages have been migrated.
Redirects: https://github.com/vercel/front/pull/45728
2025-05-15 15:20:00 +01:00
9c757f6d5c
Docs IA 2.0: Server and Client Components ( #79143 )
...
Closes:
- https://linear.app/vercel/issue/DOC-4655/client-components
- https://linear.app/vercel/issue/DOC-4656/server-components
- https://linear.app/vercel/issue/DOC-4657/composition-patterns
Redirects: https://github.com/vercel/front/pull/45564
This PR:
- Adds new **Server and Client Components** page to **Getting Started**
- Explains how Server and Client components are rendered
- Clarifies when to use them
- Reviews and simplifies composition patterns (examples)
- Improves the **How does PPR work** section in light of static,
dynamic, and streaming.
2025-05-15 14:26:19 +01:00
24dd546207
Docs: Fix page order in Getting Started ( #79240 )
2025-05-15 12:21:47 +00:00
0dcee14044
docs: add graceful error boundary example ( #77781 )
...
This adds an example in the documentation for the errors page for a
graceful error boundary in Next.js.
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
### Adding or Updating Examples
- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas )
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs )
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
---------
Co-authored-by: Zack Tanner <1939140+ztanner@users.noreply.github.com >
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2025-05-14 08:44:07 -07:00
04a19c1260
docs: Move Edge Runtime information to API reference ( #79152 )
...
Closes: https://linear.app/vercel/issue/DOC-4658/edge-runtime
Redirects: https://github.com/vercel/front/pull/45645
---------
Co-authored-by: Lee Robinson <lee@leerob.com >
2025-05-14 12:35:09 +00:00
0e39e7f155
Docs: Visual nits ( #79198 )
...
Fix missing heading and line highlighting
2025-05-14 11:57:41 +01:00
e3667265e7
Docs: Change mjs codeblocks to js ( #79163 )
...
Closes:
https://linear.app/vercel/issue/DOC-4450/missing-syntax-highlighting-on-mjs-codeblocks
It looks like shiki doesn't really support `mjs` code blocks. For now,
we keep the filename with `.mjs` extension, but change to `js` code
block type.
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2025-05-14 09:05:40 +01:00
dd0c9881ac
docs: Fix grammar in vitest.mdx (How to set up Vitest with Next.js) ( #78654 )
...
This PR fixes a tiny grammar mistake on the [**How to set up Vitest with
Next.js**](https://nextjs.org/docs/app/guides/testing/vitest ) page:
Before | After
--- | ---
[...] we recommend using an **E2E tests** for `async` components. |
[...] we recommend using **E2E tests** for `async` components.
The article "an" should not be used before a plural noun.
2025-05-13 11:52:14 -07:00
73e87727b7
docs: improve 'use client' directive and client components ( #79115 )
...
### Why?
Our docs mention the `'use client'` directive to "designate a Client Component," but this can easily lead to misunderstanding that the users need to mark the directive to write a Client Component. This chains to ambiguity on the concept that the entry point Client Components' props must be serializable.
It is essential to emphasize that this directive serves as the **entry point** for the client-server **boundary**, not a Client Component opt-in feature.
2025-05-13 15:51:28 +02:00
260ba8667f
docs: use single quote for 'use client' directive ( #79114 )
...
### Why?
Most of the code snippets were using single quotes, so unify and match the usage.
Also, React [docs](https://react.dev/reference/rsc/use-client ) uses a single quote.
2025-05-13 15:45:58 +02:00
9173eb10c3
Docs: Add PPR page to getting started section ( #79076 )
...
Closes: https://linear.app/vercel/issue/DOC-4653/partial-prerendering
Related: https://linear.app/vercel/issue/DOC-4555/ppr-and-dio
Redirects: https://github.com/vercel/front/pull/45481
- Creates a placeholder page for PPR in Getting Started.
- Reviews and updates content
- Adds examples
2025-05-13 08:51:42 +01:00
f3ad435ff3
docs: Merge CSS pages ( #78996 )
...
Closes: https://linear.app/vercel/issue/DOC-4648/css
Redirects: https://github.com/vercel/front/pull/45417
- Improves the CSS content for clarity and brevity.
- Adds Pages Router examples.
---------
Co-authored-by: Lee Robinson <lee@leerob.com >
2025-05-12 08:32:57 -05:00
75658b8115
docs: Delete empty optimizing folder ( #78966 )
...
Cleaning up 🧹
2025-05-08 10:18:31 -05:00
48e739089c
Docs: Fix headings in Getting Started ( #78965 )
2025-05-08 16:06:15 +01:00
3bf570d84d
Docs IA 2.0: Images ( #78769 )
...
Closes:
- https://linear.app/vercel/issue/DOC-4626/images
- https://linear.app/vercel/issue/DOC-4610/split-image-and-font-pages
Redirects: https://github.com/vercel/next.js/pull/78769
**Housekeeping:**
- Deletes BYA images page
- Creates relevant getting started docs in `/pages`
- Splits "Images and Fonts" into "Images" and "Fonts" pages to allow us
to add more context to each page in the future
**API reference**:
- Improves image API reference to follow more of a consistent format and
language
- Adds examples
**Follow-up:** https://github.com/vercel/next.js/pull/78857
- Create a Deep Dive Guide on how image optimization works
---------
Co-authored-by: Rich Haines <hello@richardhaines.dev >
2025-05-08 13:11:38 +01:00
0236e18567
fix CSP docs ( #78937 )
...
This is erroneously showing the app router docs for pages router,
however nonce handling was not added to pages router (support is being
added in #78936 ) and the included examples are using server components.
2025-05-07 15:31:39 -07:00
6f4729effb
docs: Create tailwind guide ( #78908 )
...
Closes: https://linear.app/vercel/issue/DOC-4643/tailwind
Redirects: https://github.com/vercel/front/pull/45246
2025-05-07 08:55:21 -05:00
d05288de2e
Docs IA 2.0: Metadata ( #78905 )
...
Closes: https://linear.app/vercel/issue/DOC-4642/metadata
Redirects: https://github.com/vercel/front/pull/45244
- Expands `generateMetadata` API reference to describe behavior
- Adds new examples to the `ImageResponse` API reference
- Create JSON-LD guide
---------
Co-authored-by: Rich Haines <hello@richardhaines.dev >
2025-05-07 11:58:32 +01:00
6e3af1b0fe
Docs IA 2.0: Fonts ( #78899 )
...
Closes: https://linear.app/vercel/issue/DOC-4641/fonts
Redirects: https://github.com/vercel/front/pull/45242
2025-05-07 10:09:12 +01:00
5221bd5d4e
Update multi-zones.mdx ( #78812 )
...
To serve the static content from the right application you also need a
rewrite rule for the static assets and not only the actual content.
Fixes : #78811
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2025-05-05 17:08:30 +00:00
23d2441b3f
docs: Improve landing page, add intro to Getting Started page ( #78765 )
...
Co-authored-by: Lee Robinson <lee@leerob.com >
2025-05-02 11:38:00 -05:00
71c0e9a546
Update authentication.mdx ( #78738 )
...
Fix a bug that may confuse beginners.
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
### Adding or Updating Examples
- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas )
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs )
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
2025-05-01 03:14:50 +00:00
6c09eab829
Exclude config package from bundling ( #78671 )
...
## What?
Adds `config` to the list of packages not to bundle. Turbopack's
require/import analysis is more advanced than Webpack's and it fails to
bundle because the package require is not in a `try {}` block.
Fixes #78471
Fixes PACK-4477
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
### Adding or Updating Examples
- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas )
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs )
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
2025-04-30 08:18:05 +02:00
0d34b3cc7d
docs: improve "use server" inline example ( #78653 )
2025-04-29 10:12:30 -05:00
02d693057f
docs: link the Cloudflare adapter for Workers ( #78610 )
...
Thanks for adding a link to the Cloudflare adapter.
This PR updates the link to the adapter to link the adapter based on
OpenNext which is our current recommended solution to deploy to
Cloudflare Workers.
(The existing link was to Next on Pages which was our former solution).
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2025-04-28 17:39:54 +00:00
9434a83b69
feat: add ravendb library to server-external-packages.json ( #78319 )
...
Hello from the RavenDB team (https://github.com/ravendb/ravendb )
We've seen multiple reports of issues with Next.js and our ravendb
package. This PR resolves those issues by adding ravendb package to
`server-external-package.json`.
i've included one library.
- [ravendb](https://www.npmjs.com/package/ravendb )
let me know if any changes are needed.
2025-04-28 10:27:54 -07:00
85f087d647
docs: Add missing deprecation notice for legacyBehavior in Link component ( #78405 )
2025-04-28 10:25:29 -05:00
f7eaa860e9
Update MDX documentation to use next-mdx-remote-client ( #78347 )
...
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2025-04-28 16:15:52 +02:00
6d715f78bf
docs: add better-auth auth provider ( #74075 )
2025-04-26 15:20:16 -05:00
298d0d1670
docs: Updating to AWS Amplify Hosting ( #78564 )
2025-04-25 17:55:19 -05:00
27d2fa2838
docs: remove Vercel mentions and improve deployment page ( #78557 )
...
This PR prunes references to Vercel in the documentation. Some of the
mentions were egregious and unneeded. Others were documenting specific
behavior for how Next.js runs on Vercel, which is better suited for the
Vercel documentation.
It also restructures our deployment documentation to remove any previous
bias toward Vercel. Rather than separating self-hosting (Node.js server,
Docker, static export) into its own section from managed platforms, it
now lists them all together. Vercel is listed under "Adapters",
alongside Netlify, Cloudflare, and AWS Amplify (in alphabetical order).
These are the companies we're working with on the [Deployment Adapters
API](https://github.com/vercel/next.js/discussions/77740 ), who currently
maintain their own adapters and will eventually migrate to use this new
API. We've [started working
on](https://github.com/vercel/next.js/pull/78166 ) that API.
For different features in the docs, like ISR or Middleware, this PR also
adds a new feature matrix that shows the different deployment options
and whether this feature is supported. For example, features that
require using the server are not supported with static exports.
Additionally, when there is configuration possible (like changing the
caching behavior of ISR) we link back to our guide which explains these
options in detail.
This PR also updates the Middleware section of the self-hosting guide to
mention [Node.js runtime
support](https://nextjs.org/blog/next-15-2#nodejs-middleware-experimental ).
I've also removed the "Managed Next.js (Vercel)" entry for the docs
sidebar, as it is not necessary and Vercel should not have additional
priority there over other providers.
Netlify has confirmed they're okay with the specific feature matrix link
included in the adapters section, and I did my best to include the
Cloudflare and Amplify versions based on their documentation. If any of
the providers want to see changes to those links, please let me know and
I'll open a PR.
2025-04-25 15:28:09 -05:00
071e31705f
docs: Move caching page to deep dive ( #78537 )
...
Closes: https://linear.app/vercel/issue/DOC-4608/caching
Redirects: https://github.com/vercel/front/pull/44626
2025-04-25 10:51:30 -05:00
354b255d91
docs: Move Sass and CSS-in-JS pages to guides ( #78536 )
2025-04-25 08:16:35 -05:00
93a9e97c71
Docs IA 2.0: Create public folder API reference ( #78531 )
...
Closes: https://linear.app/vercel/issue/DOC-4604/public-folder
- Renames "Static Assets" page to "Public Folder" and moves it to the
file-system conventions section.
Redirects: https://github.com/vercel/front/pull/44623
2025-04-25 08:08:57 +01:00
7eb3ff45a9
docs: update redirected link ( #78527 )
2025-04-24 22:23:03 -05:00
9e7c0991ee
docs: Delete config page in app docs ( #78521 )
2025-04-24 14:08:34 -05:00
76ade73def
docs: Move optimizing pages to guides ( #78500 )
2025-04-24 13:40:54 -05:00
0619059568
docs: added a few legacy version tags ( #78506 )
2025-04-24 16:14:49 +01:00
2171257242
Docs: fix reference to experimental.turbo ( #78507 )
...
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
### Adding or Updating Examples
- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas )
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs )
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
2025-04-24 16:13:02 +02:00
Delba de Oliveira