Skip to content

[codex] Use dynamic footer copyright years#3754

Merged
Kitenite merged 2 commits intomainfrom
polar-stop
Apr 26, 2026
Merged

[codex] Use dynamic footer copyright years#3754
Kitenite merged 2 commits intomainfrom
polar-stop

Conversation

@saddlepaddle
Copy link
Copy Markdown
Collaborator

@saddlepaddle saddlepaddle commented Apr 26, 2026

Summary

  • Replaces the legacy web footer hardcoded copyright year with new Date().getFullYear().
  • Replaces the shared email footer hardcoded copyright year with new Date().getFullYear().
  • Leaves historical/legal dates and vendor/license copyright notices unchanged.

Root Cause

The legacy web footer used a static year string, which would require another manual update when the year changes. The shared email footer had the same rolling-year issue.

Impact

Website and email footer copyright years now stay current without annual manual patches.

Validation

  • bunx @biomejs/biome@2.4.2 check 'apps/web/src/app/(dashboard-legacy)/components/Footer/Footer.tsx' packages/email/src/components/layout/StandardLayout/components/Footer/Footer.tsx
  • Scanned footer copyright output for remaining hardcoded © 20xx strings.

Summary by CodeRabbit

  • Chores
    • Footer now displays the current year dynamically instead of a fixed year, ensuring copyright stays up to date.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 26, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2c56e6d1-bec7-4746-9999-b53bf645754e

📥 Commits

Reviewing files that changed from the base of the PR and between c34fb82 and ce9cc7e.

📒 Files selected for processing (2)
  • apps/web/src/app/(dashboard-legacy)/components/Footer/Footer.tsx
  • packages/email/src/components/layout/StandardLayout/components/Footer/Footer.tsx

📝 Walkthrough

Walkthrough

Footer components were changed to compute and render the current year at runtime (using new Date().getFullYear()) instead of rendering fixed year literals. No other layout, styling, or functionality changes were made.

Changes

Cohort / File(s) Summary
Web App Footer
apps/web/src/app/(dashboard-legacy)/components/Footer/Footer.tsx
Replaced hard-coded copyright year (2025) with a runtime-calculated currentYear = new Date().getFullYear() in the rendered text.
Email Package Footer
packages/email/src/components/layout/StandardLayout/components/Footer/Footer.tsx
Replaced hard-coded copyright year (2026) with a runtime-calculated currentYear = new Date().getFullYear() in the rendered text.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 I nibble time as seasons steer,
A nimble year appears on here,
From fixed to fleeting, fresh and clear,
The Footer hops — the now is near!

🚥 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
Title check ✅ Passed The title clearly and accurately summarizes the main change: updating the footer year from 2025 to 2026, which is concise and directly related to the changeset.
Description check ✅ Passed The description provides comprehensive information including summary, root cause, impact, and validation steps, though it omits some template sections like 'Type of Change' and 'Testing'.
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 docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch polar-stop

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

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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 26, 2026

🚀 Preview Deployment

🔗 Preview Links

Service Status Link
Neon Database (Neon) View Branch
Vercel API (Vercel) Open Preview
Vercel Web (Vercel) Open Preview
Vercel Marketing (Vercel) Open Preview
Vercel Admin (Vercel) Open Preview
Vercel Docs (Vercel) Open Preview

Preview updates automatically with new commits

@saddlepaddle saddlepaddle marked this pull request as ready for review April 26, 2026 05:54
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Apr 26, 2026

Greptile Summary

Updates the hardcoded copyright year in Footer.tsx from 2025 to 2026, aligning the legacy dashboard footer with the current release year. The fix is correct, but the year remains a static string — a dynamic new Date().getFullYear() expression would eliminate the need for this class of change in future years.

Confidence Score: 5/5

Safe to merge — minimal single-line change with no functional risk.

Only finding is a P2 style suggestion to use a dynamic year expression; no correctness or reliability concerns.

No files require special attention.

Important Files Changed

Filename Overview
apps/web/src/app/(dashboard-legacy)/components/Footer/Footer.tsx Single-line change updating hardcoded copyright year from 2025 to 2026; correct but still hardcoded (dynamic year would avoid future manual updates)

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Footer.tsx renders] --> B["© 2026 Superset (hardcoded)"]
    B --> C[Displayed in legacy dashboard footer]
    style B fill:#f9f,stroke:#333
Loading
Prompt To Fix All With AI
This is a comment left during a code review.
Path: apps/web/src/app/(dashboard-legacy)/components/Footer/Footer.tsx
Line: 7

Comment:
**Hardcoded year will need another manual update next year**

The copyright year is still a static string, meaning this same patch will be needed again next year. Using `new Date().getFullYear()` keeps the footer perpetually accurate without future manual changes:

```suggestion
			<p className="text-sm text-muted-foreground">© {new Date().getFullYear()} Superset</p>
```

How can I resolve this? If you propose a fix, please make it concise.

Reviews (1): Last reviewed commit: "Update web footer year" | Re-trigger Greptile

<footer className="mt-auto w-full border-t border-border/50 py-5">
<div className="mx-auto flex w-[95vw] max-w-screen-2xl items-center justify-between">
<p className="text-sm text-muted-foreground">© 2025 Superset</p>
<p className="text-sm text-muted-foreground">© 2026 Superset</p>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Hardcoded year will need another manual update next year

The copyright year is still a static string, meaning this same patch will be needed again next year. Using new Date().getFullYear() keeps the footer perpetually accurate without future manual changes:

Suggested change
<p className="text-sm text-muted-foreground">© 2026 Superset</p>
<p className="text-sm text-muted-foreground">© {new Date().getFullYear()} Superset</p>
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/web/src/app/(dashboard-legacy)/components/Footer/Footer.tsx
Line: 7

Comment:
**Hardcoded year will need another manual update next year**

The copyright year is still a static string, meaning this same patch will be needed again next year. Using `new Date().getFullYear()` keeps the footer perpetually accurate without future manual changes:

```suggestion
			<p className="text-sm text-muted-foreground">© {new Date().getFullYear()} Superset</p>
```

How can I resolve this? If you propose a fix, please make it concise.

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

@saddlepaddle saddlepaddle changed the title [codex] Update web footer year [codex] Use dynamic footer copyright years Apr 26, 2026
@Kitenite Kitenite merged commit d3753d0 into main Apr 26, 2026
12 of 13 checks passed
MocA-Love added a commit to MocA-Love/superset that referenced this pull request Apr 26, 2026
3 PR (#442, #443, #444) で取り込み済みの 9 commits を git 履歴上もマージ済みに記録する。
内容差分は無し (merge -s ours)。

取り込み内容:
- 6b96acd Improve sidebar group management UX (superset-sh#3745)
- a4079e7 Update dashboard sidebar workspace icons (superset-sh#3755)
- d3753d0 [codex] Use dynamic footer copyright years (superset-sh#3754)
- ce606be Handle browser passthrough during v2 resize (superset-sh#3744)
- b1e1eb7 Refactor v2 workspace page (superset-sh#3747)
- 8693869 [codex] move v2 toggle to experimental settings (superset-sh#3748)
- ef3f381 Revert "fix(desktop): refit v2 terminal after font settle (superset-sh#3742)" (superset-sh#3750) - 手動移植 (vibrancy patch 維持)
- 25b2d52 Show terminal sessions from all workspaces in dropdown (superset-sh#3751)
- 62737db fix v1 terminal resize repaint (superset-sh#3756)
@Kitenite Kitenite deleted the polar-stop branch May 6, 2026 04:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants