fix(deps): update nextjs monorepo to v15.1.2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
@next/bundle-analyzer (source)	devDependencies	patch	15.1.0 -> 15.1.2
eslint-config-next (source)	devDependencies	patch	15.1.0 -> 15.1.2
next (source)	dependencies	patch	15.1.0 -> 15.1.2

---

Release Notes

vercel/next.js (@​next/bundle-analyzer)

v15.1.2

Compare Source

v15.1.1

Compare Source

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

v15.1.2

Compare Source

v15.1.1

Compare Source

vercel/next.js (next)

v15.1.2

Compare Source

v15.1.1

Compare Source

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - "* 0-3 * * 1" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the Next.js monorepo to v15.1.2, including @next/bundle-analyzer, eslint-config-next, and next packages across multiple apps.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Updated @next/bundle-analyzer package to v15.1.2.	Updated version in package.json. Updated lockfile to reflect the change.	apps/blog/package.json yarn.lock
Updated eslint-config-next package to v15.1.2.	Updated lockfile to reflect the change.	yarn.lock
Updated next package to v15.1.2.	Updated version in respective package.json files. Updated lockfile to reflect the change.	apps/blog/package.json apps/cv/package.json apps/insights/package.json yarn.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
blog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 23, 2024 5:28am
cv	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 23, 2024 5:28am
insights	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 23, 2024 5:28am

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!