chore(deps): bump next from 16.2.7 to 16.2.9

[dependabot]

Bumps next from 16.2.7 to 16.2.9.

Release notes

Sourced from next's releases.

v16.2.9

Empty release to ensure next@latest points at a stable release. Next.js only allows publishing with Trusted Publishing enabled. In order to fix NPM dist-tags, we have to release a new version. Updating dist-tags is not possible with Trusted Publishing.

v16.2.8

Release with no changes in an attempt to fix next@latest pointing at a prerelease version.

Commits

• f37fad9 v16.2.9
• d9aaaed [cd] Allow tagging semver-lower releases as @latest if @latest po… (#94627)
• 6f16804 v16.2.8
• 0dbc1d5 [16.2.x][cd] Ensure release can be triggered on old branches (#94598)
• 90e3c81 [16.2.x] Align Actions dependencies with Canary (#94339)
• 83f402c [16.2.x][cd] Stop fetching all tags when searching parent tag (#94334)
• 411c455 v16.2.7
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by CodeRabbit

• Chores
  • Updated framework dependency to a newer patch version for enhanced stability and bug fixes.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the Next.js dependency in the web application from version 16.2.7 to 16.2.9. The change is a straightforward patch version bump with no modifications to application code, configuration, or other dependencies.

Changes

Dependency Updates

Layer / File(s)	Summary
Next.js version update apps/web/package.json	Next.js dependency is bumped from 16.2.7 to 16.2.9.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• OpenDevFlow/md-latex#44: Previous next dependency version bump in the same file from 16.2.6 to 16.2.7.

Suggested reviewers

• hiranyasemindi
• iamvirul

Poem

🐰 A little hop and a skip away,
Next.js now runs on a newer day,
Sixteen point two point nine so fine,
Patches applied, all lines align! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title clearly and concisely describes the main change: bumping the Next.js dependency from version 16.2.7 to 16.2.9, which matches the changeset exactly.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/npm_and_yarn/next-16.2.9

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

apps/web/package.json (1)

27-27: ⚡ Quick win

Align eslint-config-next with the bumped Next.js patch version.

After changing next on Line 27 to 16.2.9, eslint-config-next remains 16.2.6 (Line 48). Please verify and preferably pin it to the same patch to avoid lint/config drift across Next-managed rules.

Suggested follow-up change

   "devDependencies": {
@@
-    "eslint-config-next": "16.2.6",
+    "eslint-config-next": "16.2.9",

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/web/package.json` at line 27, Update the package.json dependency so that
"eslint-config-next" is pinned to the same Next.js patch version as "next"
(change "eslint-config-next" from 16.2.6 to 16.2.9), then reinstall dependencies
(npm/yarn/pnpm install) to ensure the lockfile is updated; confirm linting still
runs against the updated config. Refer to the JSON keys "next" and
"eslint-config-next" in package.json when making the change.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@apps/web/package.json`:
- Line 27: Update the package.json dependency so that "eslint-config-next" is
pinned to the same Next.js patch version as "next" (change "eslint-config-next"
from 16.2.6 to 16.2.9), then reinstall dependencies (npm/yarn/pnpm install) to
ensure the lockfile is updated; confirm linting still runs against the updated
config. Refer to the JSON keys "next" and "eslint-config-next" in package.json
when making the change.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: eb687b29-c359-46f1-8bcb-7054b572c21c

📥 Commits

Reviewing files that changed from the base of the PR and between a63bfb7 and 555e69e.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• apps/web/package.json