[ocavuebot]

Adds two iOS items to the 0.18.0 What's New list and asks future PRs to update the list.

What's New items (0.18.0)

• Faster, smoother gestures (iOS): groups the smoothness work from 0.17.0 and 0.18.0. 0.17.0 had no What's New, so this is the first place users hear about it.
  • 0.18.0: swiping between days (fix(mobile): make swiping between days smoother #1939, refactor(mobile): render only mounted day slides #1937), the week strip (fix(mobile): make the week strip scroll smoothly #1957)
  • 0.17.0: swipe back (fix(mobile): make swipe back smoother #1793), row swipe actions (fix(mobile): make row swipe actions smoother #1792, fix(mobile): keep swipe rows from stopping half open in WebKit #1926), bottom sheets (fix(mobile): make bottom sheets smoother #1794), image lightbox drag (fix(mobile): drag the image lightbox without re-rendering per move #1785)
• Sheets with depth (iOS): the drawer depth effect (feat(mobile): add drawer depth effect #1954).

The existing "What's New" item stays first. Desktop still shows only that item.

Docs

• AGENTS.md: a PR that adds a feature or a change users will notice also adds a WHATS_NEW item for the next marketing version.
• CONTRIBUTING.md: one bullet that points to it.

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

Summary by Sourcery

Highlight the latest iOS user-facing improvements in the 0.18.0 What's New list and establish guidance for maintaining it.

New Features:

• Add iOS What's New entries highlighting smoother gestures and depth-enhanced sheets for version 0.18.0.

Enhancements:

• Document the expectation that user-visible changes include a corresponding What's New item.

Documentation:

• Update contributor guidance to explain how and when to add What's New items.

[coderabbitai]

Caution

Review failed

The pull request is closed.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

[sourcery-ai]

Reviewer's Guide

Updates the 0.18.0 in-app What's New list with two iOS items—grouped smoothness improvements and sheet depth—and documents the requirement for future user-visible changes to add appropriately versioned, platform-scoped entries.

Flow diagram for adding versioned What's New items

flowchart LR
    Change[User-visible change] --> Version[Next marketing version]
    Version --> WhatsNew[WHATS_NEW]
    WhatsNew --> Platform[Platform-scoped item]
    Platform --> IOS[iOS: Smoother everywhere]
    Platform --> Depth[iOS: Depth behind sheets]
    Docs[AGENTS.md and CONTRIBUTING.md] --> Change

Loading

File-Level Changes

Change	Details	Files
Adds two iOS-facing entries to the 0.18.0 in-app What's New content, preserving the existing entry as the first item.	Combines smoothness improvements from versions 0.17.0 and 0.18.0 into a single user-facing item. Documents the iOS sheet depth effect as a separate item. Scopes both new entries to iOS while leaving desktop with the existing item.	packages/app/src/whats-new/whats-new-content.ts
Documents the expectation that user-noticeable changes include a What's New entry.	Defines the target file, marketing-version keying, platform scoping, and concise copy guidelines. Adds a contributing guide reference to the new workflow.	AGENTS.md CONTRIBUTING.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[qodo-code-review]

ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing

[sourcery-ai]

Sorry @ocavue, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 5 days by commenting @sourcery-ai review. Upgrade to get a review now.

[cubic-dev-ai]

1 issue found across 3 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="CONTRIBUTING.md">

<violation number="1" location="CONTRIBUTING.md:43">
P3: This requires an item for every user-noticeable change, while `AGENTS.md` explicitly excludes small fixes. Align this rule with those exclusions so contributors know whether to document a user-visible small fix.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic</sub>

[cubic-dev-ai]

P3: This requires an item for every user-noticeable change, while AGENTS.md explicitly excludes small fixes. Align this rule with those exclusions so contributors know whether to document a user-visible small fix.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At CONTRIBUTING.md, line 43:

<comment>This requires an item for every user-noticeable change, while `AGENTS.md` explicitly excludes small fixes. Align this rule with those exclusions so contributors know whether to document a user-visible small fix.</comment>

<file context>
@@ -40,6 +40,9 @@ message and, for `feat`/`fix`, the user-facing changelog entry.
 - The changelog is scoped to `apps/desktop/`: a change that should appear in it
   must touch that directory. A pure `packages/core` fix still ships in the next
   release, but gets no changelog line.
+- A change users will notice also adds an item to the in-app What's New list
+  (`packages/app/src/whats-new/whats-new-content.ts`). See
+  [AGENTS.md](AGENTS.md#development-workflow).
</file context>

Suggested change

	- A change users will notice also adds an item to the in-app What's New list
	- A user-noticeable feature or substantial change (not an internal change, refactor, or small fix) also adds an item to the in-app What's New list