GITHUB RELEASE INSTRUCTIONS
# 🚀 GitHub Release Creation Instructions for v1.3.0
## Manual Release Creation Steps
Since the gh CLI version is outdated (v0.0.4), follow these steps to create the GitHub release manually:
### 1. Go to GitHub Releases Page
Navigate to: `https://github.com/clduab11/gemini-flow/releases/new`
### 2. Release Configuration
- **Tag version**: `v1.3.0`
- **Release title**: `🚀 Gemini-Flow v1.3.0: Complete Google Services Integration & AI Coordination Framework`
- **Target**: `clduab11/issue4` (current branch)
### 3. Release Description
Copy the content from `/Users/chrisdukes/Desktop/projects/gemini-flow/GITHUB_RELEASE_v1.3.0.md`
### 4. Upload Release Assets
Upload these files from the `release-assets/` directory:
- `gemini-flow-v1.3.0.tar.gz` (8.5MB - Source code archive)
- `gemini-flow-docs-v1.3.0.tar.gz` (559KB - Documentation archive)
- `checksums.txt` (189B - Asset verification checksums)
### 5. Release Options
- ✅ Check "Set as the latest release"
- ✅ Check "Create a discussion for this release"
- ⭕ Leave "Set as a pre-release" unchecked (this is a stable release)
### 6. Verification Checklist
Before publishing, verify:
- [ ] Tag `v1.3.0` exists in repository
- [ ] All 3 release assets are uploaded
- [ ] Release notes are comprehensive and professional
- [ ] Version matches package.json (1.3.0)
- [ ] Checksums are included for asset verification
### 7. Publish Release
Click "Publish release" to make it live.
## Post-Release Actions
### 1. NPM Package Publicationwhen to use it
Community prompt sourced from the open-source GitHub repo clduab11/gemini-flow (MIT). A "GITHUB RELEASE INSTRUCTIONS" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
clduab11/gemini-flow · MIT