Skip to content

Conversation

@validbeck
Copy link
Collaborator

@validbeck validbeck commented Jan 15, 2026

Pull Request Description

What and why?

sc-13925

While adding the copyright info to the documentation files, we realised that the notebooks that are commonly dispersed to users as "capsule" files do not have this info. I updated:

  • All the notebooks in notebooks minus the "mini-templates" that get pulled together by the end-to-end notebook generation notebook
  • The copyright.txt file that contains the updated copyright info

How to test

Pull down this PR and click on any full notebook file. Jump to the bottom to see the updated copyright info:
Screenshot 2026-01-15 at 12 19 58 PM

For example:

What needs special review?

n/a

Dependencies, breaking changes, and deployment notes

Release notes

n/a

Checklist

  • What and why
  • Screenshots or videos (Frontend)
  • How to test
  • What needs special review
  • Dependencies, breaking changes, and deployment notes
  • Labels applied
  • PR linked to Shortcut
  • Unit tests added (Backend)
  • Tested locally
  • Documentation updated (if required)
  • Environment variable additions/changes documented (if required)

@validbeck validbeck self-assigned this Jan 15, 2026
@validbeck validbeck added the internal Not to be externalized in the release notes label Jan 15, 2026
@github-actions
Copy link
Contributor

PR Summary

This pull request uniformly updates the copyright headers across a large number of files in the repository. The changes adjust the copyright years from "2023-2024" to "2023-2026" and modify the accompanying commentary to emphasize referring to the LICENSE file in the repository for details. These updates improve clarity and ensure that the copyright notices remain current without altering the runtime behavior or logic of the code.

Test Suggestions

  • Run the full test suite (unit, integration, and end-to-end tests) to verify that no functionality has been inadvertently affected by the header changes.
  • Perform a code search for any residual outdated copyright headers.
  • Verify that documentation and automated tools that parse headers still function as expected.

Copy link
Collaborator

@nrichers nrichers left a comment

Choose a reason for hiding this comment

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

Copyright footer changes LGTM but AFAIK updating the copyright year to 2026 is not a hard requirement, as copyright doesn't magically expire. Still a nice change to have, though.

I left one comment about the wordiness of the copyright footer, please take a look. Unlike the Python files, which cannot link directly to the LICENSE file, the notebooks can use a link and so the text should not need to explain where to find the link target - that's the purpose of the link after all.

I assume you didn't check with a license scanning tool if this copyright footer gets found? I believe most modern license scanners will detect SPDX-License-Identifier in a Jupyter Notebook cell if it's in plain text, so this change should be OK. That said, if you can check, that might be useful.

Copy link
Contributor

@cachafla cachafla left a comment

Choose a reason for hiding this comment

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

Wow, lots of files 😄

Awesome.

@validbeck validbeck merged commit 4903205 into main Jan 16, 2026
29 checks passed
@validbeck validbeck deleted the beck/sc-13925/add-copyright-footer-to-notebooks branch January 16, 2026 05:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Not to be externalized in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants