standard_ledger 0.5.0 → 0.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 89af058a7d94051bc75f8e853d1be397270b52bc5a02020dfdd41484c6cacda5
-  data.tar.gz: 50eef558981621f3561c42095d294f87f09d7ed18e8fc5a5919c0801262f257b
+  metadata.gz: 8f6aa5d56ba73fe170790d016b50f00aec95f563346a08c36f8823d05fbddd98
+  data.tar.gz: dc1ef4c96e69b6a8d4832ce1f80dc6a979d63dc25ff059ed77794b829f414e7f
 SHA512:
-  metadata.gz: 16d8c529a99909adb4739feb0ea76e996ebd709c044bc56dd2722bc041f4c17670d2bb383a48072df9a686bc02b1c2a49add8206618ddeb7fb86dd2b45e61c9f
-  data.tar.gz: 5f152b064c69e8da3f7e2767c4b3914da197599ed64ecc8e512be6c34e334af25337f83fd68080c7811a3f4772df647d5799ae635cb0116409286455bd86bf0e
+  metadata.gz: 54f927af7564ee7e9319a2fd87358a86e91ab55c7d3fea872dc9f821efc40cde0cd31b55cdf4b90e7bfb138bb501a7e9888358a2645f27c662058ba2fd2ef869
+  data.tar.gz: 108ce4c242c054512e6f3f173cf683dc9f71ee08882ed82dd505be092af6fb08f7b97b635aa5685ed5c08f7257e6ad285d327a2b4a9bd1f07c2ee1bcfcda19d2

data/CHANGELOG.md

@@ -6,6 +6,109 @@ project adheres to [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [0.6.0] - 2026-09-24
+
+A breaking release. The declarative projection engine is removed, and the gem
+now ships only what its four consumers use: `Entry`, `post`, `Projection`,
+`refresh!`, `Config`, the events, and the RSpec matcher. Before this release,
+every consumer's `main` (jumpdrive-web, sidekick-web, fundbright-web,
+luminality-web) was grepped (app, lib, config, spec, db). None of them
+referenced anything listed under **Removed**.
+
+### Removed
+- **Projection DSL:** `StandardLedger::Projector`, `projects_onto`,
+  `standard_ledger_projections`, `standard_ledger_projections_for`, and the
+  `Projector::Definition` struct.
+- **All projection modes:** `StandardLedger::Modes::Inline`, `::Async`, `::Sql`,
+  `::Trigger`, `::Matview` (its refresh logic moved to the private
+  `StandardLedger::Matview`), and `:manual`.
+- **Jobs:** `StandardLedger::ProjectionJob` and
+  `StandardLedger::MatviewRefreshJob`. The gem no longer depends on `activejob`
+  (or declares `concurrent-ruby` directly).
+- **`StandardLedger.rebuild!`**. `Projection#rebuild` stays as a method your own
+  code calls.
+- **Test-mode overrides:** `StandardLedger.with_modes`,
+  `StandardLedger.mode_override_for`, `StandardLedger.reset_mode_overrides!`,
+  `StandardLedger::RSpec::Helpers`, and the `before(:each)` hook that
+  `require "standard_ledger/rspec"` used to register. The file now defines only
+  the `post_ledger_entry` matcher.
+- **`rake standard_ledger:doctor`** and `StandardLedger::Engine`. The engine
+  had no routes or tables, and its initializer was a no-op. The install
+  generator still works without it.
+- **Errors:** `StandardLedger::PartialFailure` (never raised) and
+  `StandardLedger::UnhandledKind` (only raised by the projection DSL).
+- **Config:** `default_async_job`, `default_async_retries`, and `scheduler`.
+  None of them was read by anything outside the engine, and no consumer
+  initializer sets them (jumpdrive-web's generated initializer only has them
+  as comments).
+- **Events:** `<prefix>.projection.applied` and `<prefix>.projection.rebuilt`
+  (only the engine emitted them). `entry.created`, `projection.refreshed` and
+  `projection.failed` are unchanged.
+- `StandardLedger.post` no longer reports `projections[:inline]`. It always
+  passes `projections: {}`. The keyword is still passed to `result_adapter`,
+  so existing six-keyword adapters keep working.
+
+### Added
+- `StandardLedger.refresh!(view, concurrently: :auto)` uses
+  `REFRESH MATERIALIZED VIEW CONCURRENTLY` only when it can succeed: no open
+  transaction, the view is populated (`pg_class.relispopulated`), and it has a
+  valid unique index without a `WHERE` clause or expressions (`pg_index`).
+  Otherwise it runs a plain refresh. If the catalog probe raises, the error is
+  reported through `Rails.error` (`handled: true`, `severity: :warning`,
+  `source: "standard_ledger"`) and the refresh falls back to plain. This
+  replaces the rescue-and-retry around `PG::ObjectNotInPrerequisiteState` /
+  `RefreshInsideTransaction` in sidekick-web's `RefreshMaterializedViewsJob`.
+  It was verified against PostgreSQL 17 for an empty view, unique, non-unique,
+  partial and expression indexes, a refresh inside a transaction, and a
+  missing view.
+- `Config#matview_refresh_strategy` accepts `:auto`.
+
+### Changed
+- `refresh!` now raises `ArgumentError` for an unknown `concurrently:` value
+  or an unknown `matview_refresh_strategy`. Before, an unknown strategy
+  silently meant a blocking refresh.
+- `RefreshInsideTransaction`'s message now suggests `concurrently: :auto`.
+- The gemspec summary, description, README, design doc, `AGENTS.md`, and
+  `docs/MIGRATION_GUIDE.md` now describe the slimmed gem. The design doc keeps
+  a history section on the removed engine (§8).
+
+### Upgrade note (0.5.x → 0.6.0)
+1. Bump to `gem "standard_ledger", "~> 0.6"`. No consumer on 2026-09-24
+   referenced anything removed, so no application code changes are needed.
+2. **Sorbet/Tapioca apps:** regenerate the RBIs (`bin/tapioca gem
+   standard_ledger` and `bin/tapioca dsl`). Delete any stale
+   `sorbet/rbi/dsl/standard_ledger/{projector,projection_job,matview_refresh_job}.rbi`.
+   All four consumers carry these today, and they describe constants that no
+   longer exist, so `tapioca dsl --verify` will flag them.
+3. If your initializer sets `c.default_async_job`, `c.default_async_retries`
+   or `c.scheduler`, delete the line (it now raises `NoMethodError`). The
+   generated initializer only has them as comments, which you can remove too.
+4. Optional: replace hand-rolled "try CONCURRENTLY, fall back to plain"
+   logic with `StandardLedger.refresh!(view, concurrently: :auto)`, or set
+   `c.matview_refresh_strategy = :auto`.
+5. If you ever did depend on the engine, pin `~> 0.5` and see git tag
+   `v0.5.1` and design doc §8.
+
+## [0.5.1] - 2026-09-24
+
+### Fixed
+- The `post_ledger_entry` RSpec matcher now listens on the channel
+  `StandardLedger::EventEmitter` emits through. It only subscribed to
+  `ActiveSupport::Notifications`, but on Rails 8.1+ the gem emits through
+  `Rails.event.notify`, so the matcher saw no events at all: every positive
+  expectation failed and every `not_to post_ledger_entry` passed without
+  checking anything. When `EventEmitter.rails_event_available?` is true, the
+  matcher now subscribes a collector to `Rails.event` for the block and
+  unsubscribes it afterwards.
+
+### Documentation
+- README **Testing** section (and `AGENTS.md`) said the RSpec support hook
+  calls `StandardLedger.reset!`. It calls `reset_mode_overrides!`, which keeps
+  host initializer configuration intact.
+- The engine initializer comment now tells hosts to subscribe via
+  `Rails.event.subscribe` on Rails 8.1+ rather than
+  `ActiveSupport::Notifications.subscribe`.
+
 ## [0.5.0] - 2026-09-22
 
 ### Changed
@@ -446,7 +549,9 @@ roadmap.
   and `:trigger` (host-owned, gem records rebuild SQL).
 - `standard_ledger:doctor` rake task (verifies trigger presence, etc.).
 
-[Unreleased]: https://github.com/rarebit-one/standard_ledger/compare/v0.5.0...HEAD
+[Unreleased]: https://github.com/rarebit-one/standard_ledger/compare/v0.6.0...HEAD
+[0.6.0]: https://github.com/rarebit-one/standard_ledger/compare/v0.5.1...v0.6.0
+[0.5.1]: https://github.com/rarebit-one/standard_ledger/compare/v0.5.0...v0.5.1
 [0.5.0]: https://github.com/rarebit-one/standard_ledger/compare/v0.4.0...v0.5.0
 [0.4.0]: https://github.com/rarebit-one/standard_ledger/compare/v0.3.0...v0.4.0
 [0.3.0]: https://github.com/rarebit-one/standard_ledger/compare/v0.2.0...v0.3.0