Skip to content
This repository was archived by the owner on Mar 2, 2026. It is now read-only.

Add version tracking and auto-bump workflow#6

Merged
simons-plugins merged 1 commit into
mainfrom
feature/version-update-notifications
Feb 21, 2026
Merged

Add version tracking and auto-bump workflow#6
simons-plugins merged 1 commit into
mainfrom
feature/version-update-notifications

Conversation

@simons-plugins

@simons-plugins simons-plugins commented Feb 21, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add VERSION file (1.0.0) for tracking skill version
  • Add GitHub Action to auto-increment patch version on merge to main
  • Enables update notifications in Claude Code statusline

Test plan

  • Verify VERSION file contains 1.0.0
  • Verify bump-version workflow triggers on merge and increments patch

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Introduced automated patch version management for the main branch, which automatically increments the version number with each deployment. Version updates can be skipped when specified in commit messages.
    • Project version file established to track releases.

Add VERSION file (1.0.0) and GitHub Action to auto-increment patch version on merge to main. Supports update notifications in Claude Code statusline.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@simons-plugins simons-plugins merged commit e45a746 into main Feb 21, 2026
1 of 4 checks passed
@coderabbitai

coderabbitai Bot commented Feb 21, 2026

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

A new GitHub Actions workflow is introduced to automatically increment the patch version in a VERSION file on main branch pushes, excluding commits with [skip bump] in the message. The VERSION file is created with initial version 1.0.0.

Changes

Cohort / File(s) Summary
Version Management Setup
.github/workflows/bump-version.yml, VERSION
Adds automated version bumping workflow that reads VERSION file, increments patch component, exposes NEW_VERSION, and commits changes to main. Includes skip condition for [skip bump] in commit messages. VERSION file initialized with 1.0.0.

Sequence Diagram

sequenceDiagram
    participant GitHub as GitHub Actions
    participant Repo as Git Repository
    participant FS as File System
    participant Git as Git Operations

    GitHub->>Repo: Trigger workflow on push to main
    GitHub->>FS: Checkout repository
    FS->>GitHub: Repository checked out
    GitHub->>FS: Read VERSION file
    FS->>GitHub: Return version (1.0.0)
    GitHub->>GitHub: Parse and increment PATCH<br/>(1.0.0 → 1.0.1)
    GitHub->>FS: Write updated VERSION file
    FS->>GitHub: File written
    GitHub->>GitHub: Set NEW_VERSION output variable
    GitHub->>Git: Commit VERSION change<br/>[skip bump] flag
    Git->>Repo: Create commit
    GitHub->>Git: Push to main
    Git->>Repo: Update main branch
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 A version we set, a number to track,
Automation hops in, bumping patch by patch,
One-oh-oh starts our journey true,
Each push to main makes something new!

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/version-update-notifications

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@simons-plugins simons-plugins deleted the feature/version-update-notifications branch February 21, 2026 13:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant