[tylercschneider]

Context

The published 0.1.0 dates from 2026-06-25 and predates the split between authoring and runtime. 41 merges have landed since, none of them released, and [Unreleased] was empty — so the changelog now covers the whole span.

Nothing currently on main is installable from RubyGems, which is why event_engine-subscribers cannot pin a working dependency.

What's in it

Events are now declared with event_engine-event_definition and compiled into a committed catalog. This gem builds a validated event from that catalog and hands it to a processor. How an event is processed is declared by the host in config/event_rules.yml, resolved event → pack → default.

Added — processing rules and the rules file, the processor registry, pack discovery, DefinitionPublisher registered at boot, event_engine:rules:check, and errors that name the fix.

Changed (breaking) — process_type comes from the rules file rather than the schema; EventDefinition::Schema → CatalogEntry; the engine is now a Railtie; schema:catalog → catalog.

Removed (breaking) — the authoring layer, the three processor config accessors, SubjectRegistry and define_subjects, the markdown printer, and dead ProcessType / EventSchemaMerger.

Full detail in the changelog entry.

Minor bump per 0.x convention.

Verification

Suite green: 134 runs, 174 assertions, 0 failures.

gem build succeeds and produces event_engine-0.2.0.gem.

The whole pipeline was verified end to end from a clean slate in a scratch Rails app against main — generate, catalog, rules check, and an emit reaching both an inline subscriber and a background job.

Release order

Publish after event_engine-event_definition 0.3.0, since pack discovery reads Definition.pack_schema_paths, which does not exist in that gem's published 0.2.0. Then event_engine-subscribers 0.1.0, which will pin event_engine >= 0.2.0.

🤖 Generated with Claude Code