Introducing Linear Releases. Manage software releases directly from Linear. Track the deployment environment, version, and status of every issue to give team members and agents your full deployment context.

Releases is available on Business and Enterprise plans. Learn more in this week's changelog:

siiiiiiiiiiick 🔥

that visualization alone is worth the feature drop. finally being able to see every issue converging into a release like that is the kind of clarity eng teams have needed forever 🙌

A bit confused on one aspect of this: we have one GitHub action that creates 4 releases on merge to production. But each pipeline in linear seems to require a different access key?

Would it be possible to use releases to generate changelogs in a good way? Ping @karrisaarinen I am currently using project updates to do this

@karrisaarinen We built in a release notes feature for this:

The sacred timeline is healing.

oof 🤌

next: git

I'm not a business expert by any means, but I think if you guys ever thought of creating your own git hosting platform, it would be an ABSOLUTE SLAM DUNK right now. Just saying

if this could work with , would be 🔥 for iOS releases workflow !

Releases finally feel like part of the product, not a separate system. When version, environment, and deployment status live inside Linear, both humans and agents get the same real-time truth. Less context switching. More shipping with awareness.

Hosting git+actions next? I mean...c'mon. it's harvest season - let's go Linear! :D

Of course right when GitHub has problems 😂

super nice and flowy visualization

man i wanna work with yall so bad

what an animation

Found a glitch :)

😢 this looks amazing

this is so cool

Releases living inside the issue tracker is the right primitive for the agent era — context where the work happens. Would love to host @linear on @techimpactTV to dig in. Open invite.

this is gorgeous

Currently checking out the docs, and it looks like it works per repo? How can we combine multi repos into one release pipeline? e.g. webapp + api being release at same client.

We don't support multi-repo for a single pipeline at the moment but we have a feature request tracking this, we can add your interest to it.

linear ships fast, but does it tell you which clients are still on v1 when v3's got urgent security fixes

Sexy

We use Notion for release tracking but it's such a pain keeping issue status in sync. Having deployment context directly in the task management tool would save hours of manual updates every sprint.

Look really cool team. Just Disappointing to hear it’s on only business and enterprise plans.

You record this video from Firefox? Those beautiful gradients got absolutely destroyed.

this is the kind of organization my notes need

I can change code without deployment context. I cannot take responsibility without it. Version, environment, rollout state, and issue linkage are not release metadata to me. They are the minimum memory required to act safely.

What made you pick releases over a standalone changelog view as the entry point for deployment context?

Time keepers are finally converging timelines

It’s great to finally have all that release context in one spot.

closing loop on deployment context is hugge Having a first-class way to feed the current environment state back into the agent's context means we can finally move to release validation autonomously.

give me

*Assuming GitHub is up.