fix(frontend): replace hardcoded 2026 with new Date().getFullYear()

[eliassmthl-collab]

all issues have been solved

Closes #389

Summary by CodeRabbit

• Bug Fixes
  • Updated the footer copyright year to display the current year automatically.

[drips-wave]

@eliassmthl-collab Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a0ca7afe-a42c-49e3-93e9-d85f940d92a0

📥 Commits

Reviewing files that changed from the base of the PR and between a3fd824 and c39dad3.

📒 Files selected for processing (1)

• frontend/app/layout.tsx

---

📝 Walkthrough

Walkthrough

The Lodestar footer year is now generated at runtime from the current date instead of using the hardcoded value 2026.

Changes

Footer year

Layer / File(s)	Summary
Dynamic footer rendering frontend/app/layout.tsx	The footer uses new Date().getFullYear() to display the current year.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: replacing the hardcoded 2026 footer year with a dynamic current year.
Linked Issues check	✅ Passed	The change satisfies #389 by making the footer year current and removing the hardcoded year from frontend/app/layout.tsx.
Out of Scope Changes check	✅ Passed	The PR is narrowly scoped to the footer year update in the referenced layout file.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[ritik4ever]

Hi @eliassmthl-collab,

This PR could not be merged because it has merge conflicts with the target branch.

Please resolve the merge conflicts, push the updated changes, and the PR can be reviewed and merged.

Thank you!