docs: Automatically update copyright years

[MortGron]

Description

For many years it has been like this:

With this change, the copyright year will automatially be set to the current year:

The start year is the year of the first tagged version of the SDK: 2017

To use a year range would be consistent with the Cognite home page:

Checklist:

• Tests added/updated.
• Documentation updated. Documentation is generated from docstrings - these must be updated according to your change.
  If a new method has been added it should be referenced in cognite.rst in order to generate docs based on its docstring.
• The PR title follows the Conventional Commit spec.

[gemini-code-assist]

Summary of Changes

Hello @MortGron, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modernizes the documentation's copyright display by implementing an automatic update mechanism. Instead of a static year, the copyright will now dynamically show a range from the SDK's first tagged version (2017) to the current year. This change also necessitated an upgrade of the Sphinx documentation generator and its associated dependencies, ensuring compatibility and leveraging newer features.

Highlights

• Automated Copyright Year: The documentation's copyright year has been updated to automatically reflect the current year, displayed as a range from 2017 to the present.
• Sphinx Version Upgrade: The minimum required Sphinx version for documentation generation has been upgraded from 7.2 to 8.1.
• Dependency Updates: Various documentation and linting dependencies have been updated, including a Poetry version bump and adjustments to Sphinx-related packages.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• docs/source/conf.py
  • Updated the minimum required Sphinx version.
  • Modified the copyright string to dynamically display a year range.
• poetry.lock
  • Updated the Poetry version used for dependency management.
  • Added markers for the pyyaml package.
  • Upgraded the sphinx package version and its Python compatibility.
  • Updated various sphinxcontrib and linting-related dependencies.
  • Refreshed the content hash to reflect dependency changes.
• pyproject.toml
  • Updated the Sphinx dependency version within the documentation group.

Activity

• The PR description indicates that documentation has been updated.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request automates the copyright year update in the documentation by using Sphinx's %Y placeholder, which is a good improvement. The related dependency updates for Sphinx and other packages are also included and appear correct. The changes are straightforward and I have no comments.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 48.86%. Comparing base (baecf3d) to head (2fd919e).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2480      +/-   ##
==========================================
- Coverage   48.90%   48.86%   -0.04%     
==========================================
  Files         191      191              
  Lines       26157    26157              
==========================================
- Hits        12792    12782      -10     
- Misses      13365    13375      +10     

see 4 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[haakonvt]

🦄 great!