Skip to content

chore: add CI workflow with REUSE compliance and canary job#8

Merged
jimsynz merged 1 commit into
mainfrom
chore/add-ci
Jan 13, 2026
Merged

chore: add CI workflow with REUSE compliance and canary job#8
jimsynz merged 1 commit into
mainfrom
chore/add-ci

Conversation

@jimsynz
Copy link
Copy Markdown
Contributor

@jimsynz jimsynz commented Jan 13, 2026

Summary

  • Add GitHub Actions workflow with REUSE compliance check
  • Include canary job for unified branch protection across the organisation
  • All actions pinned by SHA per OSSF scorecard requirements

This aligns the proposals repo with the organisation-wide branch protection strategy.

@jimsynz jimsynz merged commit bcdc0a1 into main Jan 13, 2026
2 checks passed
jimsynz added a commit that referenced this pull request May 18, 2026
Jido v2.0 (Feb 2026) and follow-ups landed several breaking changes
after the proposal was accepted:

- `actions:` option removed from `use Jido.Agent`; capabilities now
  live inside Plugins (Skill→Plugin rename)
- `handle_instruction/2` and `handle_signal/2` agent callbacks gone;
  replaced by `signal_routes:` plus `Jido.Plugin.handle_signal/2`
- `Jido.Agent.run_action/3` no longer public; agents use `cmd/2`
  (pure) or signal dispatch through `AgentServer`
- Instance-scoped supervision: `{Jido, name: MyApp.Jido}` plus
  `Jido.start_agent/3`
- Built-in actions moved from `Jido.Actions.*` to `Jido.Tools.*`
- `jido_action` and `jido_signal` now standalone packages

Revises the worked examples (Manipulator, Coordinator, Simple Agent,
AI Planning, supervision), introduces `BB.Jido.Plugin.Robot` as the
v0.1 integration surface (replacing the `BB.Jido.Agent` macro), bumps
the version pin to `~> 2.2`, expands the API corrections table, and
resolves open question #8 (sensors vs PubSubBridge).
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