studio-engine 0.143.1 → 0.143.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 761f94ad92a6df45d0a165787da06d6c9e22c9bd633d0f5e620bc5415aa864d7
-  data.tar.gz: c89ffc8d2c2ebc525810aae86582fb1fbd3f6f4287ab56030a2ffea4797ef7db
+  metadata.gz: d143f0f1859ecc3107721013965ab60cfdc991f7bee318fee274361278e98cc1
+  data.tar.gz: 32c057de7990555e9a8ff3a54963ba6916e0bba30fc26489a46c783def9fb5f8
 SHA512:
-  metadata.gz: 566e603bb66c08bb7ec329542bb16f9e4efc2d244e7644fa0bf6649655699ef221fd61423a2efc34f74957fa0dde7d6f752a6265cba7d4685a2f9251f026378f
-  data.tar.gz: 41e5bfc37d8940a2a2dcab2d40f324ec6dd64d3917dea0516f99aca1441afa7596cbdaa25bac94471d93b7c667515e5c5d4b2e69c32905a6ef89184516162e0b
+  metadata.gz: d0857709512f2a2180b6d1c25aeb9c886ba6708550cc00560243d5881d0422e900c77145823e31018aab7d334133deb8087fc3cbcaebfa79a5ef332ce15ecef1
+  data.tar.gz: d500cb012588520e9c8d76974f9a5f8189560288216b584a6712a609393b0dbed749e10bf1b33bb590932dbfc4cadf632a86ad448053dafa476fbb956a78128b

data/CHANGELOG.md

@@ -4,6 +4,8 @@ The format is [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). This pro
 
 ## Unreleased
 
+## 0.143.2 — 2026-11-10
+
 ## 0.143.1 — 2026-11-10
 
 ## 0.143.0 — 2026-11-10

data/Gemfile

@@ -94,11 +94,14 @@ end
 # — by 3h, 2h20m, 14h15m and 1h10m — and the worst case was not the longest but
 # the fastest, a lock that went stale 36 minutes after the previous fix was
 # committed. While it is stale EVERY open engine PR is red, over a line no PR
-# author owns. So .github/dependabot.yml now opens the bump PR daily (scoped to
-# solana-studio ALONE, so this repo never inherits the third-party graveyard),
-# and .github/workflows/engine-lock-automerge.yml merges it when — and only
-# when — all four of bin/lock-bump-mergeable's conditions hold. A breaking bump
-# still stops, stays open and red, and still waits for a human.
+# author owns. So every solana-studio release now moves this lock itself:
+# `bin/release ship` (mcritchie-studio bin/release.rb, step 5d,
+# settle_producer_locks -> bump_producer_locks_for_accepted) runs
+# `bundle lock --update solana-studio --conservative` on this repo's `accepted`
+# the moment the final is live, and warns by name when it cannot. That replaced
+# a daily, solana-studio-only Dependabot check and its auto-merge lane (task
+# ci-runs-reactive-and-once, 2026-11-10), which arrived up to a day late. A lock
+# that still trails is drift, handled by the dependency-update SOP.
 group :development, :test do
   gem "solana-studio", ">= 0.5.3"
 end

data/lib/studio/version.rb

@@ -1,3 +1,3 @@
 module Studio
-  VERSION = "0.143.1"
+  VERSION = "0.143.2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: studio-engine
 version: !ruby/object:Gem::Version
-  version: 0.143.1
+  version: 0.143.2
 platform: ruby
 authors:
 - Alex McRitchie
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-11-10 00:00:00.000000000 Z
+date: 2026-11-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails