Skip to content

ci: release pin bumps instead of filing them as chores - #104

Closed
ryzizub wants to merge 1 commit into
chore/full-very-good-analysisfrom
ci/release-pin-bumps
Closed

ryzizub wants to merge 1 commit into
chore/full-very-good-analysisfrom
ci/release-pin-bumps

Conversation

@ryzizub

@ryzizub ryzizub commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

Description

Stack 6 of 6 for #68. Base: chore/full-very-good-analysis (#102).

Raised in review on #100. The bot titled its pull request chore: bump pinned plugins, and chore does not bump a version, so a pin bump never reached a release. A pin bump is how a user gets new skills and agents, which makes it a fix for them.

Needs squash merges to work as intended, since the squashed commit takes the pull request title.

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore
  • 🧪 Test

🤖 Generated with Claude Code

The bot titled its PR `chore: bump pinned plugins`, and `chore` does not bump a
version, so a pin bump never reached a release. A pin bump is how a user gets
new skills and agents, which makes it a `fix` for them.
@ryzizub
ryzizub added this pull request to stack #103 October 26, 2026 13:28
@ryzizub
ryzizub marked this pull request as ready for review October 26, 2026 13:28
@ryzizub ryzizub closed this Oct 26, 2026
An error occurred while trying to automatically change base from chore/full-very-good-analysis to main October 28, 2026 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant