update footer copyright year from 2025 to 2026

[himanshujays29]

Update footer copyright year to 2026

Fixes #751

Changes done:

• Updated the footer configuration to change the copyright year from 2025 to 2026
• Synced footer year with the current year to avoid outdated information

Screenshots

Not applicable (text-only configuration change)

Preview Link(s):

• _config.yml

✅️ 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 (config-only change)
• Tried squashing the commits into one

Summary by CodeRabbit

• Chores
  • Updated copyright year in footer from 2025 to 2026.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The copyright year in the footer configuration was updated from 2025 to 2026 in the _config.yml file. The footer_content variable was modified to reflect the current year while maintaining all other textual content unchanged. This is a single-line configuration update affecting the copyright notice displayed in the project footer.

Possibly related PRs

• Update footer year to 2025 (#734) #735: Updates the same footer_content field in _config.yml with a year increment from 2024 to 2025, following an identical pattern of annual copyright year updates.

🚥 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 title 'update footer copyright year from 2025 to 2026' directly and clearly summarizes the main change in the changeset.
Linked Issues check	✅ Passed	The PR updates footer_content in _config.yml from 2025 to 2026, which aligns with the linked issue #749 requirement to update the copyright year.
Out of Scope Changes check	✅ Passed	The PR changes are limited to updating the copyright year in the footer configuration, which is directly related to the linked issue objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6a01b5d and 0b8e232.

📒 Files selected for processing (1)

• _config.yml

🔇 Additional comments (1)

_config.yml (1)

83-83: LGTM!

The copyright year update from 2025 to 2026 is correct and aligns with the current year. This addresses issue #749 appropriately.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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.}

[tachyons]

Thanks, and Happy new year 🎆

[himanshujays29]

Thank you! @tachyons, Happy New Year 🫡