Skip to content

Update project copyright to 2026#79

Open
GYFX35 wants to merge 1 commit intomainfrom
update-copyright-2026-12489973793321031995
Open

Update project copyright to 2026#79
GYFX35 wants to merge 1 commit intomainfrom
update-copyright-2026-12489973793321031995

Conversation

@GYFX35
Copy link
Copy Markdown
Owner

@GYFX35 GYFX35 commented Feb 26, 2026

This PR updates the copyright year to 2026 in the following locations:

  • frontend/templates/index.html (Footer copyright)
  • translations/en/LC_MESSAGES/messages.po (Header copyright)
  • translations/es/LC_MESSAGES/messages.po (Header copyright)
  • README.md (Example prompt in documentation)
  • Recompiled translation binaries (.mo files) to reflect header changes.
  • Verified changes visually and ensured existing tests pass.

PR created automatically by Jules for task 12489973793321031995 started by @GYFX35

Summary by Sourcery

Update copyright notices to reference the year 2026 across user-facing content and templates.

Chores:

  • Refresh footer copyright year in the main HTML template to 2026.
  • Update example footer copyright year in the README to 2026.
  • Regenerate and update translation message files to reflect the new copyright year in headers.

…ocumentation.

Co-authored-by: GYFX35 <134739293+GYFX35@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Feb 26, 2026

Deploying ai-services with  Cloudflare Pages  Cloudflare Pages

Latest commit: 60c3113
Status: ✅  Deploy successful!
Preview URL: https://37aa576b.ai-services-36y.pages.dev
Branch Preview URL: https://update-copyright-2026-124899.ai-services-36y.pages.dev

View logs

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Feb 26, 2026

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
❌ Deployment failed
View logs
aiservices 60c3113 Feb 26 2026, 06:53 PM

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai bot commented Feb 26, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates all user-facing and translation header copyright strings from 2024 to 2026, including regenerating compiled translation binaries.

File-Level Changes

Change Details Files
Bump documentation example footer copyright year to 2026.
  • Update the example YAML footer line to use © 2026 instead of © 2024 in the README documentation snippet.
README.md
Update frontend footer copyright year to 2026.
  • Change the main HTML footer text to display © 2026 UsingAI instead of © 2024 UsingAI.
frontend/templates/index.html
Align translation catalog metadata with new copyright year and regenerate binaries.
  • Adjust copyright year in English PO header metadata to 2026.
  • Adjust copyright year in Spanish PO header metadata to 2026.
  • Recompile corresponding MO files so runtime translations reflect the updated headers.
translations/en/LC_MESSAGES/messages.po
translations/es/LC_MESSAGES/messages.po
translations/en/LC_MESSAGES/messages.mo
translations/es/LC_MESSAGES/messages.mo

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-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.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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.

1 participant