source-command-update-infos-release

Use this skill when the user asks to run the migrated source command update-infos-release.

Command Template

Release Management Workflow

Automate Codex releases tracking and guide version management.

Usage

/update-infos-release          # Update CC releases only (no guide version bump)
/update-infos-release patch    # Update CC + bump guide patch (3.9.11 → 3.9.12)
/update-infos-release minor    # Update CC + bump guide minor (3.9.11 → 3.10.0)
/update-infos-release major    # Update CC + bump guide major (3.9.11 → 4.0.0)

Workflow Steps

1. Check for New Codex Releases

bash
./scripts/update-cc-releases.sh

If new versions detected, continue. Otherwise, stop.

2. Update Codex Releases Tracking

Files to update:

• machine-readable/Codex-releases.yaml
• guide/Codex-releases.md
• Codex-ultimate-guide-landing/index.html (badge + section)

Process:

1. Read latest release notes from the command output
2. Extract version, date, and highlights (2-4 key features max)
3. Update YAML with condensed highlights
4. Update Markdown with expanded details
5. Update landing badge version
6. If major features, update landing #releases section (keep top 5)

Condensation rules for YAML:

• ⭐ Major features get star emoji
• Breaking changes → breaking: array
• Bug fixes → single line
• 2-4 highlights max (focus on user-facing changes)
• Skip internal/SDK changes unless breaking

3. Guide Version Bump (if requested)

If bump-type specified:

bash
# Read current version
cat VERSION

# Bump version
# patch: 3.9.11 → 3.9.12
# minor: 3.9.11 → 3.10.0
# major: 3.9.11 → 4.0.0

# Update VERSION file
echo "X.Y.Z" > VERSION

# Sync version across docs
./scripts/sync-version.sh

Files synced by script:

• README.md
• guide/cheatsheet.md
• guide/ultimate-guide.md
• machine-readable/reference.yaml

4. Update CHANGELOG.md

Add entry:

markdown
## [X.Y.Z] - YYYY-MM-DD

### Documentation

- **Codex Releases**: Updated tracking to vA.B.C
  - [Feature 1]
  - [Feature 2]
  - [Feature 3]

[If guide version bump:]
### Version Bump

- Bumped guide version: [old] → [new]
- Reason: [major features added / significant updates / breaking changes in CC]

4.5. Add RSS Entry (for notable CC releases)

Add an entry to src/data/rss-entries.ts in the landing repo only if at least one of:

• Release has ⭐ feature(s)
• Release has breaking changes
• Release has ≥3 highlights

If none of these → skip (patch/bugfix-only releases don't need an RSS entry).

Entry format:

typescript
{
  type: 'guide_release',
  title: 'Codex vX.Y.Z',
  date: 'Mon DD, YYYY',
  description: '[1-2 sentences: main feature(s), plain text no HTML]',
  link: 'https://cc.bruniaux.com/releases/#vX.Y.Z',
},

Prepend at the top of the rssEntries array.

5. Verify Synchronization

bash
./scripts/check-landing-sync.sh

Expected output:

✅ Version guide:    X.Y.Z
✅ Templates:        N
✅ Quiz questions:   N
✅ Guide lines:      N
✅ Codex:      vA.B.C

If mismatches, fix before committing.

6. Commit and Push

Two repositories to update:

Guide Repository

bash
cd /Users/florianbruniaux/Sites/perso/Codex-ultimate-guide

git add \
  VERSION \
  CHANGELOG.md \
  README.md \
  guide/cheatsheet.md \
  guide/ultimate-guide.md \
  guide/Codex-releases.md \
  machine-readable/reference.yaml \
  machine-readable/Codex-releases.yaml

# If version bump:
git commit -m "release: vX.Y.Z

- Update Codex releases tracking (vOLD → vNEW)
- [Bump type]: vOLD_GUIDE → vNEW_GUIDE
- Update CHANGELOG with release details

Co-Authored-By: Codex Sonnet 4.5 <noreply@anthropic.com>"

# If CC releases only:
git commit -m "docs: update Codex releases to vA.B.C

- Update latest tracked version: vOLD → vNEW
- Add vNEW highlights: [feature1], [feature2], [feature3]
- [Any breaking changes or fixes]
- Update dates: YYYY-MM-DD

Co-Authored-By: Codex Sonnet 4.5 <noreply@anthropic.com>"

git push

Landing Repository

bash
cd /Users/florianbruniaux/Sites/perso/Codex-ultimate-guide-landing

git add index.html

git commit -m "chore: sync with guide vX.Y.Z

- Update Codex version badge: vOLD → vNEW
[If releases section updated:]
- Update releases timeline with vNEW features
- Maintain top 5 notable releases
- Maintain landing/guide synchronization

Co-Authored-By: Codex Sonnet 4.5 <noreply@anthropic.com>"

git push

7. Summary Output

Display to user:

✅ Release Update Complete

Guide Repository:
- Version: [old] → [new]
- Codex: vA.B.C
- Commit: [hash]
- Files: [count] updated

Landing Repository:
- Codex badge: vA.B.C
- Commit: [hash]
- Files: [count] updated

Synchronization: ✅ All synced

Next Steps:
1. Verify GitHub Pages deployment: https://florianbruniaux.github.io/Codex-ultimate-guide-landing/
2. Check version badge displays correctly
3. [If major release] Update social media / announcements

Error Handling

If no new Codex versions:

ℹ️ No new Codex releases detected.
Current tracked: vX.Y.Z
Latest available: vX.Y.Z

Aborting. Nothing to update.

If sync check fails:

❌ Synchronization check failed:
[List mismatches]

Please fix manually before committing.
Run: ./scripts/check-landing-sync.sh

If git operations fail:

❌ Git operation failed: [error]

Manual intervention required.
Check: git status

Examples

Example 1: Update CC releases only

User: /update-infos-release

Output:
✅ New Codex release detected: v2.1.15
   Date: 2026-01-22
   Highlights:
   - New feature X
   - Fix for Y
   - Improvement Z

Updating tracking files...
✅ YAML updated
✅ Markdown updated
✅ Landing badge updated

Verifying sync... ✅ All synced

Committing changes...
✅ Guide: commit abc1234
✅ Landing: commit def5678

✅ Release Update Complete

Example 2: Update CC + minor bump

User: /update-infos-release minor

Output:
✅ New Codex release detected: v2.2.0
   Major release with significant features

Current guide version: 3.9.11
Bumping to: 3.10.0 (minor)

Updating files...
✅ Codex tracking updated
✅ Guide version bumped
✅ CHANGELOG updated
✅ All docs synced

Verifying sync... ✅ All synced

Committing changes...
✅ Guide: commit abc1234 (8 files)
✅ Landing: commit def5678 (1 file)

✅ Release Update Complete (v3.10.0)

Implementation Notes

• Atomicity: If any step fails, rollback git changes (git reset --hard)
• Idempotency: Can be run multiple times safely
• Validation: Always verify sync before committing
• User confirmation: Ask before version bump if ambiguous
• Smart defaults: No bump = CC update only

Related Commands

• /version - Check current versions (guide + CC)
• /changelog - View recent CHANGELOG entries
• /sync - Run sync check without updates