Skip to content

chore(deps): bump geneva_drive from 0.6.0 to 0.9.0 - #61

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bundler/geneva_drive-0.9.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bundler/geneva_drive-0.9.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Bumps geneva_drive from 0.6.0 to 0.9.0.

Changelog

Sourced from geneva_drive's changelog.

[0.9.0]

  • Run on Sidekiq without Active Job. GenevaDrive.dispatcher = :sidekiq pushes every step as GenevaDrive::SidekiqPerformStepJob, a plain Sidekiq::Job carrying the step execution id, through Sidekiq::Client. Client middleware applies, the jid lands in job_id, and jobs are tagged with the workflow class. Supported are Sidekiq 7.3 and later 7.x, and 8.x; with any other version the dispatcher raises at boot. The default dispatcher is still :active_job.
  • Sidekiq retries are off for step jobs, since exception policies already decide reattempts. The step's exception is still raised, so Sidekiq's error handlers report it.
  • The Sidekiq dispatcher pushes synchronously, bypassing Sidekiq.transactional_push!, which would defer the push a second time from inside GenevaDrive's own after-commit callback - the double deferral already fixed for Solid Queue.
  • priority: in job options raises under the Sidekiq dispatcher, as Sidekiq has queues with weights rather than priorities.
  • Add GenevaDrive::SidekiqHousekeepingJob for running housekeeping from Sidekiq Enterprise periodic jobs or sidekiq-cron.
  • The install generator writes GenevaDrive.dispatcher = :sidekiq into a new initializer when Active Job's adapter is :sidekiq. Nothing is detected at boot, so upgrading never switches an existing app.
  • resume! now records the id of the job it pushes for an execution that was paused while scheduled. The row used to keep the previous job's id, which could already have run and done nothing, so the job behind the execution could not be found from it.
  • Fix resumable steps not handing off when Sidekiq shuts down. The executor asked Sidekiq::CLI.instance.stopping?, a method the CLI does not have (only its launcher does), so inside a sidekiq process every interruption check of a resumable step raised NoMethodError. The engine now subscribes to Sidekiq's :quiet event, which fires on TSTP (what Enterprise rolling restarts send first) and at the start of every shutdown, and resumable steps checkpoint and continue in a successor execution. This applies with either dispatcher, including Active Job on the Sidekiq adapter.
  • Create hero_id as a string column when the application's tables use string primary keys. Key type detection only recognized uuid, char(36) and varchar(36) id columns, but on SQLite an id: :string table (for example with primary_key_type: :string and UUIDv7 ids) reports a bare varchar with no length. Detection fell through to :bigint, the workflows migration created an integer hero_id, and every string hero id was silently cast to an integer on assignment, pointing workflows at the wrong hero and colliding in the ongoing-uniqueness index. The workflows migration now uses a separate geneva_drive_hero_key_type helper that returns :uuid, :string or :bigint and treats varchar/char(n)/text ids of any length as string keys. GenevaDrive's own tables keep their bigint ids. Existing installs affected by this need to change hero_id to a string column themselves.

[0.8.0]

  • Add removed_step :name for taking a step out of a workflow that has instances in flight. Deleting a step outright strands every workflow holding a scheduled execution for it: the executor finds no definition and pauses with StepNotDefinedError, which during a rolling deploy can hit every workflow sitting on that step at once. The gem cannot recover from this on its own — it knows the step is gone, but not whether the steps after it were ever meant to run, and a step's position says nothing about reachability (a capture_payment that normally ends the workflow by calling finished! sits directly before refund, so skipping forward would refund a payment that was never captured). removed_step is how the author of the removal records that judgement in advance: declared in the position the step used to occupy, it keeps the name resolvable so executions scheduled before the removal are skipped and the workflow continues to the next runnable step, while scheduling never spools an execution for the name again and before_step:/after_step: references keep working. An execution parked on the step waiting for a signal is released on resume! rather than waiting for an event that can no longer match. Workflow.removed_steps_in_flight reports which gravestones step execution rows still reference (ignoring finished and canceled workflows), so a removed_step line can be deleted once it comes back empty. The default for an undeclared removal is unchanged: the workflow still pauses.
  • Add workflow.resume_at!(:step_name) for workflows already stranded on a step that was deleted without a removed_step gravestone. Plain resume! had nowhere to send them and died with a NoMethodError on nil deep inside create_step_execution; it now raises StepNotDefinedError naming the missing step, the steps still defined, and the way out. Where to land is deliberately the operator's call, for the same reason the executor will not guess it.
  • Support MariaDB for the JSON columns (resumable step cursor, signal payload). MariaDB has no JSON type: json there is an alias for LONGTEXT with an auto-generated CHECK constraint named after the column, and since cursor is reserved in MariaDB, loading a schema dump that re-emits that constraint died on a syntax error. Rails also types such a column as text, so a Hash written to it was stored as #inspect output, which the same CHECK constraint then rejected. The installer migrations now ask for plain LONGTEXT on MariaDB via the new geneva_drive_json_column migration helper, and the models encode and decode JSON themselves whenever the column is text. The check is on the column, not the adapter, so installs that already ran the old migration on MariaDB get the encoding without having to rewrite the column.
  • Test against Rails 7.2, 8.0 and 8.1 on SQLite, PostgreSQL, MySQL and MariaDB. Previously the appraisals stopped at Rails 8.0, and the MySQL CI job could not build mysql2.

[0.7.0]

  • Add signals: external events delivered to a workflow instance with workflow.signal!(:payment_confirmed, payload: {...}, idempotency_key: event["id"]), and a step primitive that parks until one arrives with step :capture, wait_for: :payment_confirmed. Signals are rows in a new geneva_drive_signals table, persisted before any processing, so arrival order does not matter: a signal that lands before its waiting step exists is buffered and claimed when the step runs, and one that lands after the step parked wakes it immediately. Both sides of the rendezvous run under the workflow row lock, so no signal can slip through the gap, and delivery is one transaction: the insert, the waking of parked executions and every counter bump land together or not at all, so a crashed signal! leaves nothing half-delivered (the job enqueue stays after-commit, with the existing stuck-scheduled housekeeping sweep as its backstop). Waiting is a first-class step execution state (waiting) that holds no queue slot and no timer — nothing polls. Matching is by name - wait_for: also takes a GenevaDrive::SignalMatcher, whose optional block narrows by payload and is evaluated on the workflow the signal was sent to (so hero is in scope), or any other object responding to #matches?(signal). Matchers are plain reusable objects, so a rule can live in a constant and be shared across steps. Signals move pending → claimed → consumed, consumed only once every attached execution chain has finished cleanly — where skipping counts as finishing, so any flavor of skip (skip_if: at wake, skip! in a step, an exception policy, or an operator skip! on a ready or paused workflow) settles the signal that step was delivered, while skips of steps that never attached leave buffered signals alone — and in the same transaction as the step's own completion, so a reattempt or a resume! re-reads the same payload and the audit trail never claims an event was handled when it was not. Two counters on the row, claimed and consumed, count attachments and clean resolutions (with claimed? / consumed? reading those counters rather than the lifecycle state). Redelivery is deduplicated by a unique index on (workflow_id, name, idempotency_key) — the duplicate call returns the original row flagged duplicate_delivery? without dispatching. Payloads go through ActiveJob serializers, come back with indifferent access, and are bounded by GenevaDrive.max_signal_payload_size (128 KB, nil disables). signal! on a finished or canceled workflow raises GenevaDrive::WorkflowNotOngoing unless it is a redelivery of a known event; on a paused workflow the row is buffered and delivered by resume!. Timeouts are deliberately out of scope for now; waiting is instead made loud through waiting_since and two housekeeping gauges (geneva_drive.waiting_step_executions, geneva_drive.waiting_overdue past GenevaDrive.waiting_visibility_threshold, 7 days by default), with skip! and cancel! as operator escape hatches. Needs one new installer migration (the signals table plus two columns on step executions); until it runs everything else is unaffected and executing a wait_for: step raises a configuration error pointing at the missing migration. Test helpers: assert_waiting_for_signal, assert_signal_state, and the step-driving helpers now raise instead of spinning on a parked execution. Mixing up wait: and wait_for: now raises StepConfigurationError at class load in both directions, which also tightens wait: to reject Strings (previously wait: "later" silently meant zero seconds).
Commits
  • 54b477f Bump version for release
  • 4701cbb Run step jobs as native Sidekiq jobs (#44)
  • 128db5c Fix settings documented in the initializer template (fixes #40) (#42)
  • df7e49b Create hero_id as a string for string primary keys (#43)
  • 9d3609b Bump version to 0.8.0
  • 9009dd6 Move post-0.7.0 entries to Unreleased in the changelog
  • 680ffae Fix appraisals, add a default rake task and a local matrix (#37)
  • 4861885 Add removed_step for retiring steps from live workflows (#38)
  • d4dd42d Render GFM alerts in md2html
  • 79b6300 Appraisal gem lock updates
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file ruby Pull requests that update ruby code labels Oct 31, 2026
Bumps [geneva_drive](https://github.com/julik/geneva_drive) from 0.6.0 to 0.9.0.
- [Changelog](https://github.com/julik/geneva_drive/blob/main/CHANGELOG.md)
- [Commits](julik/geneva_drive@v0.6.0...v0.9.0)

---
updated-dependencies:
- dependency-name: geneva_drive
  dependency-version: 0.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/bundler/geneva_drive-0.9.0 branch from 14b59a2 to fb158e8 Compare November 18, 2026 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file ruby Pull requests that update ruby code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants