Release 24.12.0

[philippotto]

Release is built on 5d3d66d.

• Updated changelog
• Updated migration guide if applicable

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request introduces version 24.12.0 of WEBKNOSSOS, featuring enhancements in remote URI handling, asynchronous image file reading, improved error messaging, and a shift in the Terms of Service acceptance process. It also removes bounding box restrictions for super users and enhances logging for dataset operations. Several bugs have been fixed, including performance issues and incorrect segment color updates. Additionally, the integration of Google Analytics has been completely removed, indicating a change in tracking strategy.

Changes

File Path	Change Summary
CHANGELOG.released.md	Updated to reflect changes in version 24.12.0, including improvements to remote URI handling, asynchronous image reading, error message enhancements, etc.
CHANGELOG.unreleased.md	Updated to indicate unreleased changes and version reference from 24.11.1 to 24.12.0.
MIGRATIONS.released.md	Added release section for version 24.12.0, noting deprecation of googleAnalytics.trackingId.
MIGRATIONS.unreleased.md	Updated version reference to 24.12.0 and noted deprecation of googleAnalytics.trackingId.

Possibly related PRs

• Relax bounding box requirements for model training #8222: This PR modifies the bounding box requirements for model training, which is directly related to the main PR's change of removing the bounding box size restriction for super users, allowing for greater flexibility in job configurations.
• Sync dataset name with datasource in add remote view #8245: This PR ensures synchronization of dataset names in the add remote dataset view, which aligns with the main PR's updates to the dataset management functionalities, including improved error messages related to job initiation on datasets.
• Fix legacy support for outdated displayName field of datasets #8263: This PR addresses issues with the displayName field of datasets, which is relevant to the main PR's overall improvements in dataset handling and error messaging.

Suggested labels

automerge

Suggested reviewers

• daniel-wer
• MichaelBuessemeyer

Poem

🐇 In the meadow where changes bloom,
New paths for data, we make room.
With bounding boxes now set free,
And errors clearer, joyfully!
Goodbye to Google’s watchful gaze,
We hop along in brighter ways! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8c43a66 and 309722e.

📒 Files selected for processing (3)

• CHANGELOG.released.md (1 hunks)
• CHANGELOG.unreleased.md (1 hunks)
• MIGRATIONS.unreleased.md (1 hunks)

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

• MIGRATIONS.unreleased.md
• CHANGELOG.unreleased.md
• CHANGELOG.released.md

---

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

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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: 0

🧹 Outside diff range and nitpick comments (1)

CHANGELOG.released.md (1)

13-31: Consider adding bullet points for better readability

The Highlights section would be more readable if each highlight was formatted as a bullet point using - or *.

### Highlights
- When exploring remote URIs pasted from Neuroglancer, the format prefixes like `precomputed://` are now ignored, so users don't have to remove them.
- Reading image files on datastore filesystem is now done asynchronously.
- Terms of Service for Webknossos are now accepted at registration, not afterward.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2bdc9eb and 8c43a66.

📒 Files selected for processing (4)

• CHANGELOG.released.md (1 hunks)
• CHANGELOG.unreleased.md (1 hunks)
• MIGRATIONS.released.md (2 hunks)
• MIGRATIONS.unreleased.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• MIGRATIONS.unreleased.md

🔇 Additional comments (4)

CHANGELOG.unreleased.md (1)

11-11: LGTM: Version reference correctly updated.

The changelog template has been properly reset for future unreleased changes, with the version reference correctly pointing to 24.12.0.

MIGRATIONS.released.md (1)

9-13: LGTM: Migration steps properly documented.

The migration guide correctly documents:

1. The deprecation of googleAnalytics.trackingId config option
2. Links to relevant PR Remove Google Analytics #8201
3. Proper version comparison links

Let's verify if there are any remaining references to the deprecated config:

CHANGELOG.released.md (2)

10-11: LGTM!

The version header and commits link follow the standard changelog format.

---

Line range hint 33-48: LGTM!

The Added, Changed and Fixed sections follow the standard changelog format with proper bullet points and clear descriptions.

Also applies to: 50-52, 54-58

[normanrz]

So, renamable datasets will come in 25.01.0?

[philippotto]

So, renamable datasets will come in 25.01.0?

Yes, see slack discussion.