Bump VERSION to 0.2.0 — triggers first auto-release - #2
Merged
Conversation
PR #1 brought substantial changes since v0.1.0 — bumping to 0.2.0 to trigger the new auto-release workflow and produce a v0.2.0 tag + release with the current skill content. What landed since v0.1.0 (per PR #1): - Multi-platform install — new Claude.ai (web + mobile) connector section alongside Claude Desktop, Claude Code, Cursor, Windsurf, Cline, Continue.dev, ChatGPT, Gemini CLI - refresh-subscription-info default search window: 90 days → 18 months (catches annual renewals) - Full vs incremental invoice classification — prevents silent wrong per-user-cost extraction from prorated charges - Notes replace-not-append — single 'Updated from X invoice dated Y' line per app, doesn't accumulate across monthly re-runs - PDF parsing enabled (canonical case: Salesforce-billed Slack where product is only in the PDF) - Web-hosted invoices: skill asks before fetching - Real-world vendor catalog covering Slack, Notion, GitHub, Granola, Framer, Anthropic, 1Password, JumpCloud, Cloudflare, Zoom, AWS - Distributors-vs-resellers direction handling (Ingram = distributor; Bill-To field disambiguates consumption vs channel sale) - Shared billing inbox correction (Google Group on the receiver side) - Outbound-payments and other false-positive filters - CODEOWNERS routing to @shiftcontrol-dan - INSTALL/README marketing-voice rewrite, audit-log terminology removed - Auto-release workflow itself (.github/workflows/release.yaml) — what this VERSION bump exercises for the first time Merging this PR triggers release.yaml, which signs and pushes a v0.2.0 tag and creates a GitHub release with the per-skill zip attached.
|
⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done |
|
✅ I finished the code review, and didn't find any security or code quality issues. |
Branch protection on main requires the 'validate' status check, but the
previous path filter ('skills/**') meant the workflow skipped on PRs that
didn't touch skill files (like #2, which only bumps VERSION). A skipped
required workflow leaves the check pending forever, blocking merge.
Fix: run on every PR into main. The workflow is cheap (yq frontmatter
checks + a few greps), so the cost of always running is negligible.
The push trigger keeps its path filter — no need to re-run validate on
main pushes that didn't touch skills.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps top-level
VERSIONfrom0.1.0to0.2.0. On merge, this triggers.github/workflows/release.yamlfor the first time, which will:VERSION(0.2.0)v0.2.0tag doesn't exist (current latest isv0.1.0from the manual scaffold release)v0.2.0, push itskills/<name>/)v0.2.0with auto-generated notes and the zip(s) attachedWhy a MINOR bump, not PATCH
Substantive content + automation added since v0.1.0:
Pre-1.0 SemVer is flexible, but the magnitude here is more than a patch.
Type of change
Checklist
v0.2.0doesn't already existTest plan
This PR is itself the test of the auto-release workflow. After merge:
Release on VERSION bumpworkflow run on the main-branch pushv0.2.0appears under TagsIf the workflow fails for any reason, the failure is contained — no damage to repo state, no partial release. The fix would land in a follow-up PR.
Notes for the merge
Use merge commit (not squash) so the workflow's path filter sees the
VERSIONchange onmain. Squash also works because GitHub creates a new commit on main with the VERSION diff, but merge commit is the cleanest semantic.