release-open

Execute the release process for Big-AGI. Go step-by-step, waiting for user approval between major steps.

Step 1: Determine Version

If $ARGUMENTS provided, use it. Otherwise, read package.json and increment patch version.

Step 2: Gather Context

Before drafting, gather what changed:

1. git log --oneline since last release tag to see all commits
2. Fetch https://big-agi.com/changes to see what daily entries already covered
3. gh issue list --state closed --search "closed:>LAST_RELEASE_DATE" to find closed issues
4. Check auto-generated release notes (gh release create --generate-notes --draft) for community PRs and new contributors

Step 3: Update Files

1. package.json - Update version field
2. src/common/app.release.ts - Increment Monotonics.NewsVersion (e.g., 203 → 204)
3. src/apps/news/news.data.tsx - Add new entry at top of NewsItems array

For the news entry, ask user for release name and key highlights.

News entry style - Draft is a starting point, user will refine:

• Models lead when model-heavy, grouped together
• Callout features get own bullet with colon explanation
• UX items grouped, minimal bold
• Fixes last, brief
• Release name stays subtle - don't oversell the theme
• Apply the draft, then let the user edit manually and re-read after - don't over-iterate

Use <B>, <B issue={N}>, <B href='url'>. Re-read file after user edits.

1. User runs npm i to update lockfile

Step 4: README

Update README.md:

• Line ~46: Update model examples if new flagship models
• Line ~147: Add release bullet above previous version

Style: - Open X.Y.Z: **Name** feature1, feature2, feature3

Step 5: Git Operations

User commits changes, then:

git tag vX.Y.Z
git push opensource vX.Y.Z

Step 6: GitHub Release

Create release with gh release create using --notes (not --body).

Structure - discursive intro paragraph, then themed sections, not a generic "What's New" header:

# Big-AGI X.Y.Z - Name

### Theme tagline.

1-2 sentence discursive paragraph setting the release theme - what it means, not a feature list.

### Section Name (e.g., Models & Parameters)
- Bullet points for specifics
- Group by theme, not by commit order

### Vendor/Platform Section (when enough substance)
- Give a vendor its own section if 3+ related changes (e.g., Anthropic, AWS Bedrock)

### Also New
- Remaining features, scannable

## New Contributors
* @user made their first contribution (brief description) in PR_URL

**Full Changelog**: https://github.com/enricoros/big-AGI/compare/vPREV...vNEW

## Get Started
Available now at [big-agi.com](https://big-agi.com), via Docker, or self-host from source.