Linear Diffs, Figma Make, and slackening guardrails

Code review comes to Linear

The biggest story of the week is Linear Diffs, which brings full code review into Linear itself. Now you can review diffs from any issue that has a pull request, iterate on changes with agents, and sync everything back to GitHub. The new guided reviews (beta for Business/Enterprise tier) automatically reorder large PRs to surface core changes first, pushing glue code aside so you stay focused on what matters. A dedicated Reviews tab in the sidebar also sorts work by how close it is to shipping. For teams that already live in Linear for project management, this eliminates the context switch to GitHub or GitLab for review — and it's clearly designed with the agent era in mind, where AI generates large volumes of code but humans remain accountable for every merge.

Figma opens two paths to tighter design-to-code workflows

Figma shipped two significant releases that, together, signal a push toward making design tools more actionable for developers. The headliner is Figma Make, now in closed beta, which lets you visually edit your actual product and codebase. The implications are twofold: design teams can prototype directly on production code, and developers can ship changes from the prototype without re-implementing in code. Access is rolling out over the coming weeks.

Alongside Make, Figma added slot settings for component guardrails and defaults. This is a more granular design-systems feature: you can now set guardrails and default behaviors on any slot, making it harder for designers to accidentally misuse components. For teams that maintain component libraries, this reduces the friction between design intent and implementation — fewer "that's not how that component works" conversations.

The Code Connect 1.4.7 update also arrived, fixing a Kotlin 2.3 crash and adding support for passing multiple file paths to the --file flag on publish, unpublish, and parse commands — a practical quality-of-life improvement for teams syncing Figma components to multiple code files.

Slack tightens analytics and guardrails

Slack's June 2026 release (Slack June 2026) introduces a Slackbot analytics dashboard for Enterprise orgs, giving admins more visibility into how their custom Slackbot is being used. More notable from a governance perspective: members can now flag channel names, topics, and descriptions for administrative review. This is a small feature with big implications for large orgs where channel sprawl is a real problem — it gives the community a way to self-police naming conventions without relying on a few overworked admins.

The Bolt JS SDK v4.7.3 also shipped a security patch: it now rejects an empty signingSecret at initialization, preventing accidental HMAC signature forgery. If you're maintaining a Slack app, this is worth updating for.

Smaller updates across the board

Linear's mobile app got bug fixes, Notion shipped merge cells for simple tables and a bug-fix release, and the desktop Slack client got a smoothing release with incremental improvements. Nothing groundbreaking, but the steady cadence of polish across the collection continues.