Update the DB operators changelog

[Veera-mulge]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

• Documentation
  • Updated DB Operators feature announcement with refined naming conventions and removed version references.
  • Added information on transaction-ready capabilities for integration with other database operations.

[coderabbitai]

Walkthrough

This change updates a changelog entry documenting the release of DB operators. The modifications include: updating the title to emphasize "new" DB operators, removing the "v1" version reference from the introductory bullet while adjusting wording, and adding a new bullet point that describes transaction-ready capabilities and integration with other database operations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file change affecting only documentation/changelog content
• Text updates and minor rewording with no code logic or functional changes
• Homogeneous nature (consistent text edits) requires minimal reasoning per change

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Update the DB operators changelog' directly describes the main change—updating a changelog entry for DB operators with revised naming and feature descriptions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-changelog

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

src/routes/changelog/(entries)/2025-11-04.markdoc (1)

15-15: Consider clarifying the transaction-ready bullet point.

The phrasing "Transaction-ready, can be combined with other database operations" uses a comma splice and could be more explicit about the capability.

Consider this alternative for improved clarity:

-- Transaction-ready, can be combined with other database operations.
+- Can be used within transactions and combined with other database operations.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1917ab9 and 752135c.

📒 Files selected for processing (1)

• src/routes/changelog/(entries)/2025-11-04.markdoc (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: tests
• GitHub Check: build
• GitHub Check: assets

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix capitalization inconsistency in "DB Operators".

Line 3 uses "DB operators" (lowercase 'o') while line 11 uses "DB Operators" (uppercase 'O'). For consistency in user-facing documentation, standardize the capitalization throughout the document.

Apply this diff to standardize with uppercase:

-title: "Announcing new DB operators: Update multiple fields without fetching the entire row"
+title: "Announcing new DB Operators: Update multiple fields without fetching the entire row"

Also applies to: 11-11

🤖 Prompt for AI Agents

In src/routes/changelog/(entries)/2025-11-04.markdoc around lines 3 and 11, the
phrase "DB operators" is capitalized inconsistently; change both occurrences to
"DB Operators" (uppercase O) so the user-facing document uses the same
capitalization everywhere; update line 3 and line 11 to "DB Operators" ensuring
exact match and preserve surrounding punctuation and spacing.