Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ryzizub wants to merge 1 commit into from
Closed

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions .github/workflows/bot_bump_plugin_pins.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,8 +43,10 @@ jobs:
uses: peter-evans/create-pull-request@v8.1.1
with:
branch: vgvbot/bump_plugin_pins
commit-message: "chore: bump pinned plugins"
title: "chore: bump pinned plugins"
# A pin bump is how a user gets new skills and agents, so it has to
# cut a release. `chore` does not bump a version; `fix` does.
commit-message: "fix(deps): bump pinned plugins"
title: "fix(deps): bump pinned plugins"
body: |
Bump the pinned VGV plugins in `packages/plugin_source/lib/src/plugin_ref.dart` to their latest releases.

Expand Down
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,5 +161,5 @@ Each workflow under `.github/workflows/` is path-filtered, and every reusable wo
- PR titles must be [conventional commits](https://www.conventionalcommits.org). The `semantic-pull-request` job checks this, but only on PRs that trigger one of the first two workflows.
- Markdown is spell-checked with cspell against the VGV dictionaries; add project-specific words to `words` in `.github/cspell.json`. The job includes `**/*.md` and `.*/**/*.md`, excludes `bricks/**/__brick__/**`, and runs with `modified_files_only: false`, so it lints **every** markdown file whenever it runs.
- `verify-bundle` regenerates `packages/vgv_ai_cli/lib/src/templates` with `tool/generate_agents_bundle.sh` (mason_cli `0.1.3`) and fails if the committed bundle differs. Run the script whenever `bricks/agents` changes.
- The pinned plugins in `vgvPlugins` (`packages/plugin_source/lib/src/plugin_ref.dart`) are bumped by `.github/workflows/bot_bump_plugin_pins.yaml`. Every Monday it runs `packages/plugin_source/tool/bump_plugin_pins.dart`, which moves each pin to its plugin's latest GitHub release, and opens or updates one PR on `vgvbot/bump_plugin_pins`. The tool rewrites the `version` and `gitRef` lines of each `PluginRef(...)` block in place, so keep that shape when editing the file by hand.
- The pinned plugins in `vgvPlugins` (`packages/plugin_source/lib/src/plugin_ref.dart`) are bumped by `.github/workflows/bot_bump_plugin_pins.yaml`. Every Monday it runs `packages/plugin_source/tool/bump_plugin_pins.dart`, which moves each pin to its plugin's latest GitHub release, and opens or updates one PR on `vgvbot/bump_plugin_pins`, titled `fix(deps): bump pinned plugins` so that merging it cuts a release. The tool rewrites the `version` and `gitRef` lines of each `PluginRef(...)` block in place, so keep that shape when editing the file by hand.
- The bot PR is opened with the default `GITHUB_TOKEN`, so CI does not start on it by itself. Push a commit to it, or close and reopen it, before merging. Its `verify-pins` job runs `test/pinned_plugins_test.dart` (tagged `pinned-plugins`, skipped by default), which clones the real pinned plugins and translates them for every harness. Run it locally with `dart run test --run-skipped -t pinned-plugins`.
Loading