Update footer year to 2025 (#734)

[naman79820]

Fixes #734

✔️ Changes done:

Updated the footer year in _config.yml from 2024 to 2025.

Ensures the website displays the current year in the footer across all pages.

📸 Screenshots

Not applicable — this is a text-only backend/config update.

Preview Link(s):

✅️ By submitting this PR, I have verified the following

• Checked to see if a similar PR has already been opened 🤔️
• Reviewed the contributing guidelines 🔍️
• Sample preview link added (add the link(s) for all the pages changed/updated from the checks tab after checks complete)
• Tried Squashing the commits into one

Summary by CodeRabbit

• Chores
  • Updated copyright year in the footer from 2024 to 2025.

[coderabbitai]

Walkthrough

Updates the copyright year in the site footer configuration from 2024 to 2025 in _config.yml. This change addresses a stale copyright notice displayed in the website footer.

Changes

Cohort / File(s)	Summary
Configuration Update _config.yml	Updated footer_content copyright year from 2024 to 2025

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Straightforward single-value configuration update with no logic or structural changes

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: updating the footer year from 2024 to 2025 in the configuration file.
Linked Issues check	✅ Passed	The pull request successfully addresses issue #734 by updating the footer_content year from 2024 to 2025 in _config.yml, matching the expected behavior specified in the linked issue.
Out of Scope Changes check	✅ Passed	All changes in the pull request are directly scoped to resolving issue #734; only the footer year in _config.yml was updated with no extraneous modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

_config.yml (1)

83-83: Consider using a dynamic year for future-proofing.

While the current change is correct and solves the immediate issue, updating the year manually each January is error-prone. Jekyll/Liquid templates support dynamic year generation.

Consider refactoring to use Liquid's built-in site.time variable:

-footer_content: "Copyright © 2025 Contributors to CircuitVerse. Distributed under a [CC-by-sa] license."
+footer_content: "Copyright © {{ site.time | date: '%Y' }} Contributors to CircuitVerse. Distributed under a [CC-by-sa] license."

This approach automatically reflects the current year without requiring annual updates.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e76399f and 341d631.

📒 Files selected for processing (1)

• _config.yml (1 hunks)

🔇 Additional comments (1)

_config.yml (1)

83-83: Correct footer year update — ready to merge.

The footer year has been accurately updated from 2024 to 2025. The change directly resolves issue #734 and ensures the copyright notice displays the current year across all pages.