Release Story StudioGitHub to launch kitExplore the flow
Step 3

Pick the release range and add the missing context.

GitHub knows what merged. You know why it matters. The studio combines both before it writes the launch kit.

Selected range

v1.3.0 to v1.4.0

v1.3.0 to v1.4.0. 3 commits, 3 pull requests.
Example releaseTag range
This range is ready for the next step.
Available range

Changes merged this week

main@2026-05-24 to main. 3 commits, 3 pull requests.
Example releaseDate range
Use this range
After sign-in

Existing release draft

Imported GitHub data can also start from a workspace draft release.Live import only
Selected release source

v1.3.0 to v1.4.0

northstar-labs/northstar-web imported from example import with read-only source evidence.
Repository
northstar-labs/northstar-web
Strategy
Example release
Range
v1.3.0 to v1.4.0
Imported at
2026-05-29T12:05:00-04:00
Imported evidence

v1.3.0 to v1.4.0

Showing exactly what the selected range imported before generation begins.
3 pull requests3 commits3 linked issues
PR 102

Group feedback by account and pain theme

maya merged 11 files
PR 109

Add weekly planning summary panel

eli merged 8 files
PR 117

Flag stale customer follow-ups

ren merged 6 files
Release evidence

v1.3.0 to v1.4.0

Group feedback by account and pain thememaya merged PR 102
labeled source
Add weekly planning summary paneleli merged PR 109
labeled source
Flag stale customer follow-upsren merged PR 117
labeled source
Release context

Four questions, not strategy homework.

The answers travel into the next step, so the launch kit starts with repository evidence and human context together.

Release context is saved into a structured model before the kit opens.