chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
@relative-ci/agent (source)	devDependencies	patch	4.2.6 -> 4.2.7
@types/react (source)	devDependencies	minor	18.2.79 -> 18.3.1
@types/react-dom (source)	devDependencies	minor	18.2.25 -> 18.3.0
eslint-plugin-turbo (source)	devDependencies	patch	1.13.2 -> 1.13.3
i18next (source)	dependencies	patch	23.11.2 -> 23.11.3
knip (source)	devDependencies	minor	5.10.0 -> 5.11.0
pnpm (source)	packageManager	patch	9.0.5 -> 9.0.6
pnpm (source)	engines	patch	9.0.5 -> 9.0.6
react (source)	dependencies	minor	18.2.0 -> 18.3.1
react-dom (source)	dependencies	minor	18.2.0 -> 18.3.1
tsx	devDependencies	patch	4.7.2 -> 4.7.3
turbo (source)	devDependencies	patch	1.13.2 -> 1.13.3
type-fest	devDependencies	minor	4.17.0 -> 4.18.0
ws	dependencies	minor	8.16.0 -> 8.17.0

---

Release Notes

relative-ci/agent (@​relative-ci/agent)

v4.2.7: Release 4.2.7

Compare Source

What's Changed

• Update dependencies by @​vio in https://github.com/relative-ci/agent/pull/1105

Full Changelog: relative-ci/agent@v4.2.6...v4.2.7

vercel/turbo (eslint-plugin-turbo)

v1.13.3

Compare Source

i18next/i18next (i18next)

v23.11.3

Compare Source

• fix: Unsupported language is automatically added to preload option 2178

webpro/knip (knip)

v5.11.0

Compare Source

• Install peer deps in workspace (9bf286f)
• Fix some module/resolution configs in fixtures (9d319cf)
• Add support for isJSDocImportTag (introduced in TS v5.5.0) (504738d)
• No more back & forth (014ca2a)
• Back & forth (589ee17)

v5.10.1

Compare Source

• Update some dependencies (57c21b0)
• Add new arg to defaults in tests (b7db976)
• Fix storybook core.builder.name handling (resolves #​602) (8ad0406)
• Temp job with Node.js v22 + typescript v5.5-beta (21bbf28)
• Back & forth (f054070)

pnpm/pnpm (pnpm)

v9.0.6

Compare Source

facebook/react (react)

v18.3.1

Compare Source

v18.3.0

Compare Source

facebook/react (react-dom)

v18.3.1

Compare Source

v18.3.0

Compare Source

privatenumber/tsx (tsx)

v4.7.3

Compare Source

Bug Fixes

• support TS resolution in JS files when allowJs is set (#​535) (081853e)

---

This release is also available on:

• npm package (@​latest dist-tag)

vercel/turbo (turbo)

v1.13.3

Compare Source

sindresorhus/type-fest (type-fest)

v4.18.0

Compare Source

websockets/ws (ws)

v8.17.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday,before 4am on Thursday" (UTC), 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 has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
transmascfutures	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 29, 2024 3:38pm

[coderabbitai]

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[deepsource-io]

Here's the code health analysis summary for commits 0fb0e6a..68784c6. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Secrets	✅ Success		View Check ↗
JavaScript	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[relativeci]

#34 Bundle Size — 18.67MiB (~+0.01%).

68784c6(current) vs 0fb0e6a dev#31(baseline)

Bundle metrics   2 changes 1 regression

	Current #34	Baseline #31
Initial JS	1007.75KiB(~+0.01%)	1007.66KiB
Initial CSS	6.61KiB	6.61KiB
Cache Invalidation	4.01%	3.93%
Chunks	20	20
Assets	79	79
Modules	789	789
Duplicate Modules	103	103
Duplicate Code	5.62%	5.62%
Packages	81	81
Duplicate Packages	0	0

Bundle size by type   2 changes 1 regression 1 improvement

	Current #34	Baseline #31
IMG	17.4MiB	17.4MiB
JS	1.08MiB (~+0.01%)	1.08MiB
Fonts	189.64KiB	189.64KiB
CSS	6.61KiB	6.61KiB
Other	4.06KiB (-0.14%)	4.07KiB

---

Bundle analysis report Branch renovate/all-minor-patch Project dashboard

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, eval, filesystem, shell	0	454 kB	turbobot
npm/[email protected]	environment Transitive: filesystem	+6	1.03 MB	webpro
npm/[email protected]	environment	0	4.51 MB	react-bot
npm/[email protected]	environment	0	318 kB	react-bot
npm/[email protected]	Transitive: environment, filesystem, network, shell	+1	515 kB	hirokiosame
npm/[email protected]	None	0	30.6 kB	turbobot
npm/[email protected]	environment, network	0	141 kB	lpinca

🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

[kodiakhq]

This PR currently has a merge conflict. Please resolve this and then re-add the automerge label.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[github-actions]

📦 Next.js Bundle Analysis for @weareinreach/glaad

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Six Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/	7.76 KB	198.29 KB	56.65% (🟡 +0.24%)
/about	10.04 KB	200.56 KB	57.30% (🟡 +0.28%)
/act	6.67 KB	197.19 KB	56.34% (🟡 +0.16%)
/category/[tag]/[[...storyId]]	24.14 KB	214.66 KB	61.33% (🟡 +0.51%)
/story/[id]	6.44 KB	196.96 KB	56.27% (🟡 +0.37%)
/survey	69.16 KB	259.69 KB	74.20% (🟡 +0.38%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.