release notes for 2.7.1

[jleven]

Release notes for Enterprise 2.7.1

Summary by CodeRabbit

• Documentation

  • Updated release notes for FiftyOne Enterprise 2.7.1 with a release date of March 24, 2025.

• Bug Fixes

  • Addressed a security vulnerability to enhance the application's safety and reliability.

[coderabbitai]

Walkthrough

This pull request updates the release notes by adding an entry for "FiftyOne Enterprise 2.7.1" with a release date of March 24, 2025. It also documents a security fix for the identified vulnerability CVE-2025-29927 related to next.js.

Changes

File	Change Summary
docs/.../release-notes.rst	Added a new release note for "FiftyOne Enterprise 2.7.1" (release date: March 24, 2025) and noted a fix for vulnerability CVE-2025-29927 (next.js).

Possibly related PRs

• Release notes for OSS 1.4.0 / Enterprise 2.7.0 #5609: Updated release notes for "FiftyOne Enterprise 2.7.0" involving similar file changes.
• Update release-notes.rst for 1.3.1 / 2.6.1 #5518: Modified release notes for versions 2.6.1 and 1.3.1 with related file updates.

Suggested labels

documentation

Suggested reviewers

• brimoor
• findtopher

Poem

In the code, I hop with delight,
Adding notes to keep our docs bright.
A secure fix sneaks in just right,
Vulnerabilities vanish out of sight.
With a twitch of my ears, I celebrate tonight!
🐇✨

---

📜 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 d0cccf4 and 40903fc.

📒 Files selected for processing (1)

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

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

• GitHub Check: build
• GitHub Check: build

🔇 Additional comments (1)

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

6-12: Release notes properly document the security fix 👍

The release notes for 2.7.1 clearly document the security fix for the CVE-2025-29927 vulnerability related to next.js. The format is consistent with other release notes entries in the document.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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]

✅