fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@crowdin/crowdin-api-client	1.29.0 -> 1.29.2
i18next (source)	23.7.13 -> 23.7.15
next-i18next	15.1.1 -> 15.1.2
pnpm (source)	8.13.1 -> 8.14.0

---

Release Notes

crowdin/crowdin-api-client-js (@​crowdin/crowdin-api-client)

v1.29.2

Compare Source

What's Changed

• ci: fix publish wf by @​andrii-bodnar in https://github.com/crowdin/crowdin-api-client-js/pull/356

Full Changelog: crowdin/crowdin-api-client-js@1.29.1...1.29.2

v1.29.1

Compare Source

⚠️ The current build is broken. Please use the latest build instead ⚠️

What's Changed

• ci: FOSSA Dependency Analysis by @​andrii-bodnar in https://github.com/crowdin/crowdin-api-client-js/pull/354

Full Changelog: crowdin/crowdin-api-client-js@1.29.0...1.29.1

i18next/i18next (i18next)

v23.7.15

Compare Source

• types: simplifies types for array access and fixes 2103

v23.7.14

Compare Source

• types: fix types for array access

i18next/next-i18next (next-i18next)

v15.1.2

Compare Source

• fix: Install error with react-i18next v14 #​2248

pnpm/pnpm (pnpm)

v8.14.0

Compare Source

Minor Changes

• A new option added for hoisting packages from the workspace. When hoist-workspace-packages is set to true, packages from the workspace are symlinked to either <workspace_root>/node_modules/.pnpm/node_modules or to <workspace_root>/node_modules depending on other hoisting settings (hoist-pattern and public-hoist-pattern) #​7451.
• The pnpm dedupe command now accepts more command line options that the pnpm install command also accepts. Example: pnpm dedupe --store-dir=local-store-dir

Patch Changes

• The package information output by cat-index should be sorted by key.
• pnpm deploy should not touch the target directory if it already exists and isn't empty #​7351.
• pnpm add a-module-already-in-dev-deps will show a message to notice the user that the package was not moved to "dependencies" #​926 and fix #​7319.
• Don't install Node.js when use-node-version is set in a WebContainer #​7478.
• Fix copy-on-write on Windows Dev Drives #​7468.

Our Gold Sponsors

Our Silver Sponsors

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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)
glaad	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 3, 2024 2:20pm

[github-actions]

📦 Next.js Bundle Analysis for @weareinreach/glaad

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

🎉 Global Bundle Size Decreased

Page	Size (compressed)
global	189.56 KB (-1 B)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

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

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Three 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)
/about	9.06 KB	198.62 KB	56.75% (+/- <0.01%)
/gallery	29.36 KB	218.92 KB	62.55% (+/- <0.01%)
/survey	67.62 KB	257.18 KB	73.48% (+/- <0.01%)

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.