Update release-notes.rst for Teams 2.6.0

[jleven]

What changes are proposed in this pull request?

Release notes for Teams 2.6.0:

• Improved backwards compatibility between an older SDK and newer deployment.
• Added a configurable banner which appears at top and bottom of every page,
  often used for compliance reasons.
• Fixed a bug where invite email smtp configuration was not saving correctly.

Summary by CodeRabbit

• New Features

  • Introduced a configurable compliance banner that appears at both the top and bottom of every page.

• Enhancements

  • Improved backwards compatibility between older SDK versions and newer deployments.

• Bug Fixes

  • Fixed an issue with saving invite email configurations.
  • Resolved a session error that occurred before user login.

• Documentation

  • Updated release notes to include the latest version information and release dates.

[coderabbitai]

Walkthrough

This update revises the release notes documentation by adding a new section for "FiftyOne Teams 2.6.0" and updating the existing "FiftyOne Teams 2.5.1" section. The changes document enhanced backwards compatibility, a configurable compliance banner, and a fix for an issue with saving invite email SMTP configurations, along with updated release dates for both versions.

Changes

File	Change Summary
docs/.../release-notes.rst	Added new release section for "FiftyOne Teams 2.6.0" (Released February 10, 2025), updated "FiftyOne Teams 2.5.1" (Released February 3, 2025), and documented related fixes and enhancements in the release notes.

Possibly related PRs

• [docs] SMTP config #5124: Addresses issues with SMTP configuration for invitation emails.
• Update release-notes.rst for Teams 2.5.1 #5462: Involves updates to release notes for "FiftyOne Teams 2.6.0" and "2.5.1" in the same file.
• Update release-notes.rst for Teams 2.5.1 #5464: Updates release sections in docs, directly related to modifications in the release notes documentation.

Suggested labels

documentation

Suggested reviewers

• brimoor
• findtopher

Poem

I'm a bunny with a hop and a skip,
Leaping through docs on my little trip.
New release notes shine with dates so true,
Bugs fixed and banners bright in view.
Hoppy trails to code that’s fresh and new! 🐇

---

📜 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 197bfdc and fdef466.

📒 Files selected for processing (1)

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

✅ Files skipped from review due to trivial 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.

[swheaton]

🚢 🇮🇹