Update release-notes for 2.4.0

[jleven]

What changes are proposed in this pull request?

Updated release notes

How is this patch tested? If it is not, please explain why.

(Details)

Release Notes

Is this a user-facing change that should be mentioned in the release notes?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release
  notes for FiftyOne users.

(Details in 1-2 sentences. You can just refer to another PR with a description
if this PR is part of a larger change.)

What areas of FiftyOne does this PR affect?

• App: FiftyOne application changes
• Build: Build and test infrastructure changes
• Core: Core fiftyone Python library changes
• Documentation: FiftyOne documentation changes
• Other

Summary by CodeRabbit

Release Notes for FiftyOne Teams 2.4.0

• New Features
  • Added capability to set user-specific authentication headers for media queries
• Documentation
  • Updated release notes with version 2.4.0, dated January 10, 2025
• Chores
  • Updated copyright year in the footer to 2025

[coderabbitai]

Walkthrough

The pull request introduces a new release note section for "FiftyOne Teams 2.4.0" in the documentation, specifically updating the docs/source/release-notes.rst file. The release is dated January 10, 2025, and highlights a new feature that allows setting user-specific authentication headers for media queries, enhancing personalized authentication and security mechanisms within the application. Additionally, the copyright year in the footer of the HTML template has been updated to 2025.

Changes

File	Change Summary
docs/source/release-notes.rst	Added release note for FiftyOne Teams 2.4.0 with release date and new feature description
docs/source/_templates/layout.html	Updated copyright year from 2024 to 2025 in footer

Possibly related PRs

• release note cleanup #4384: Changes to release-notes.rst file
• FiftyOne Teams 1.7/FiftyOne v0.24.0 release notes #4433: Updates to release notes documentation
• Teams 1.7.1/OSS 0.24.1 release notes #4456: Modifications to release-notes.rst
• Release notes v1.0.0 #4839: Documentation updates in release notes
• Release notes v1.0.1 #4898: Changes to release-notes.rst
• Merge release/v1.0.1 to develop #4911: Merging changes in release notes
• release is now Monday #4919: Updating release dates
• updated release notes #5021: New release note section for FiftyOne Teams
• Merge v2.1.2 to develop #5023: Introduction of new release note section
• Release notes #5307: Addition of release note section
• Fix release date in docs #5313: Release notes updates

Suggested labels

documentation

Suggested reviewers

• findtopher

Poem

🐰 Release notes hop along the page,
A new version takes the stage!
Authentication headers shine bright,
FiftyOne Teams soars to new height!
Documenting progress with rabbit delight 🚀

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 529a0bd and e6063f9.

📒 Files selected for processing (1)

• docs/source/release-notes.rst (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/source/release-notes.rst

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[findtopher]

Looks great.