Main to develop 20250324

[findtopher]

What changes are proposed in this pull request?

Merge main to develop after v2.7.1 release (mostly release notes, some trailing docs)

Summary by CodeRabbit

• Documentation

  • Added a new release notes section for FiftyOne Enterprise v2.7.1, marking the release date as March 24, 2025.

• Bug Fixes

  • Included details on the resolution of a security vulnerability related to next.js (CVE-2025-29927), ensuring enhanced user security.

[coderabbitai]

Walkthrough

The changes update the release notes by adding a new section for FiftyOne Enterprise version 2.7.1, dated March 24, 2025. This section documents a fix for vulnerability CVE-2025-29927 related to next.js. No modifications were made to the declarations of exported or public entities.

Changes

File(s)	Change Summary
docs/source/release-notes.rst	Added FiftyOne Enterprise 2.7.1 release notes, including the vulnerability fix (CVE-2025-29927).

Possibly related PRs

• release notes for 2.7.1 #5640: Introduces similar release note updates for FiftyOne Enterprise 2.7.1 with the same vulnerability fix.
• Release/v1.3.2 #5572: Updates release notes for multiple versions, including changes that relate to the adjustments made for FiftyOne Enterprise 2.7.1.

Suggested labels

documentation

Suggested reviewers

• brimoor

Poem

In the burrow of code, I hop with glee,
Documenting notes for all to see.
A patch for CVE keeps our path secure,
Release notes laid out, precise and pure.
With each line of text, a hop in delight—
Rabbit-approved changes, shining so bright! 🐇🌟

---

📜 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 583976b and 308c372.

📒 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

---

🪧 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.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

docs/source/user_guide/app.rst (1)

361-364: Clarify and refine default sidebar field visibility text
The updated text now explicitly states that by default only label fields (excluding heatmaps and semantic segmentations) are visible, which improves clarity for users configuring the sidebar. There is a minor grammatical issue in line 363 ("define a dataset's a default configuration") that should be corrected (remove the extra "a").

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f4e7332 and 583976b.

📒 Files selected for processing (8)

• docs/source/brain.rst (1 hunks)
• docs/source/enterprise/data_lens.rst (1 hunks)
• docs/source/enterprise/data_quality.rst (1 hunks)
• docs/source/enterprise/query_performance.rst (1 hunks)
• docs/source/integrations/mosaic.rst (2 hunks)
• docs/source/integrations/pgvector.rst (1 hunks)
• docs/source/release-notes.rst (3 hunks)
• docs/source/user_guide/app.rst (1 hunks)

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

• GitHub Check: build

🔇 Additional comments (8)

docs/source/brain.rst (1)

395-395: New Reference Label Added
The addition of the reference label .. _brain-optimizing-lassoing-performance: enhances in-document cross-referencing and navigability. Please verify that this label is unique and that all internal links referring to this section are correct.

docs/source/integrations/pgvector.rst (2)

3-4: Improved Header Formatting
The header "Pgvector Vector Search Integration" now uses an underline with a consistent length ("==================================") that aligns with style guidelines and mirrors similar changes in related documents.

---

8-11: Enhanced Readability in Description
The description has been refactored by inserting a line break, which breaks up a long sentence and improves readability. This change makes it easier for users to digest the key points about the Pgvector extension.

docs/source/enterprise/data_quality.rst (1)

1-7: Streamlined Content by Removing Version Note
The explicit version availability note has been removed, resulting in cleaner documentation. This is consistent with similar updates in other enterprise pages and helps focus on core functionality rather than version-specific details.

docs/source/enterprise/query_performance.rst (1)

1-9: Concise Presentation of Query Performance
The removal of the explicit version availability note and subsequent minor reformatting results in a more concise presentation of the Query Performance feature. This update improves clarity and maintains consistency with related enterprise documentation.

docs/source/enterprise/data_lens.rst (1)

8-10: Improved clarity in the feature description.
The revised phrasing using "that allows you to use FiftyOne" enhances the readability and maintains consistency with the documentation style. The removal of the explicit version availability note streamlines the content without losing essential information.

docs/source/integrations/mosaic.rst (2)

4-4: Section header formatting updated.
The adjustment of the underline from a longer series of equals signs to a shorter version now better aligns with the title length, improving visual consistency in the documentation.

---

707-708: Minor formatting improvement in the code block.
Removing the extra newline after the mosaic_index.add_to_index(embeddings, sample_ids) call improves the code block’s consistency without affecting functionality.