Release on June 10, 2026

Release

Areas Affected

Media Library, Budget, Comments, Attention Items

Highlights

• The media library now supports search, making it faster to find files and AI-generated content without scrolling through everything manually.
• Images are now included in media library results, giving a more complete view of project documentation.
• Budget records now include individual line items, providing more granular financial detail at a glance.

What Changed

• Users can now search within the media library, including across AI-generated content stored there. This makes it much easier to locate specific files or responses without manually browsing the full library. (Ticket)
• Images are now displayed in media library search results and queries, giving users a complete view of all media associated with a project in one place. (Ticket)
• Budget records now include individual line items, so users can see a detailed financial breakdown rather than just top-level totals. (Ticket)
• Restored an automated background process that keeps internal environments in sync — no user-visible impact. (PR)
• Fixed an issue with the deployment pipeline to ensure updates are released reliably — no user-visible impact. (PR)
• Resolved a background validation check that was not running correctly — no user-visible impact. (PR)

---

Hotfixes Since Last Release

These fixes were deployed to production independently before this release — they are listed here for a complete record of what changed since the previous release.

June 10, 2026

• Users can now @-mention teammates directly in comments, making it easier to flag someone's attention without leaving the platform. (PR)

June 9, 2026

• Items requiring attention are now reliably surfaced in the relevant areas of the platform so that nothing requiring follow-up is missed. (PR)
• Improved how updates are queued and deployed internally to reduce the risk of release issues — no user-visible impact. (PR)
• Comments added to action items are now correctly processed and stored, ensuring they appear in the right place every time. (PR)

---

Chores

• Remove legacy branch sync solution (#290) (PR)
• auto-sync hotfix → staging via PR (#292) (PR)
• auto-sync hotfix → staging via PR (re-target to main) (#293) (PR)
• Add get_project_locations and fix observation deep link (#279) (PR)
• Merge main into staging (resolve PR #300 conflicts) (#301) (PR)
• sync main hotfix to staging (manual after conflict)
• auto-sync hotfix from main to staging