studio-engine 0.133.0 → 0.133.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 7aa30f915a5a06beddbc97ad855340b80114d9875dab7d43669596202a62f197
4
- data.tar.gz: 5737966bb7427575a76320d618e5a1221b747625c6e8393a4f2a4ede7ed4a306
3
+ metadata.gz: 4fb5298612e52f07d4d829bf6154de3fe55d44e79f9fcc7fb3fc5c64a5fc77b1
4
+ data.tar.gz: ae606171f7f2f8866e4bdf20b609192ab6da90a502357c32267f00810a1567ee
5
5
  SHA512:
6
- metadata.gz: aed3464a127458df847bcebd599605b0816e1698803c36aaa850c287cc73848c40454cd794968cf0ea4359e6f22bc3a3d56919d442c79e70dabb32fd2c0bb1de
7
- data.tar.gz: fed96340b5100692ff438bf1e40de11edee35cf3bed69260ef93520d0e004454cb4f4895cedd55c09112275dbb334b5a529796486f2bd943a92dd8019671b530
6
+ metadata.gz: 7aba4b035be637a6496b1c7e05d6bf9829a803f1566bd8192a3de247ae692e678d4387b6c8af861b1b56e763d79033c4411ab4385896bd4ba482a6eeb9ce166e
7
+ data.tar.gz: 17c221456698d97e663896658e84d22e174bf889d3ee684dc79ea9f7925cda3c8ac1a6b5212dafc427abdbbfaeafe1a2db101f5eebddf5f612bb65d5f14b89fc
data/CHANGELOG.md CHANGED
@@ -1,9 +1,19 @@
1
1
  # Changelog
2
2
 
3
- The format is [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). This project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html) — `MAJOR.MINOR.PATCH`. Consumer Rails apps install the released RubyGems package and pin the floor each one needs — the pins differ on purpose, and every consumer records why beside its own. Bumping the gem version and updating consumer lockfiles is a release; `bin/release prepare` allocates the version and does both (see [`docs/RELEASE.md`](./docs/RELEASE.md)). Write entries under `## Unreleased` and never write a version heading: when `prepare` allocates a version it rolls this file in the same commit, moving everything under `## Unreleased` beneath a new `## <version> — <date>` heading (written even when the bucket is empty) and leaving `## Unreleased` first and empty. It refuses the sweep, with nothing published, when the roll would lie or it cannot read this file; when it skips allocation, nothing rolls. [`docs/RELEASE.md`](./docs/RELEASE.md), *Rolling `Unreleased` into a version*, says when each happens and what to do by hand. `test/docs/changelog_structure_test.rb` guards the shape.
3
+ The format is [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). This project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html) — `MAJOR.MINOR.PATCH`. Consumer Rails apps install the released RubyGems package and pin the floor each one needs — the pins differ on purpose, and every consumer records why beside its own. Bumping the gem version and updating consumer lockfiles is a release; `bin/release prepare` allocates the version and does both (see [`docs/RELEASE.md`](./docs/RELEASE.md)). **Do not edit this file in a PR.** Add a fragment, `changelog.d/<slug>.<kind>.md`, instead ([`changelog.d/README.md`](./changelog.d/README.md)); `bin/changelog-check` fails a PR that adds lines under `## Unreleased`. At release, `bin/changelog-compile` folds the fragments into `## Unreleased` by kind and deletes them. Never write a version heading: when `prepare` allocates a version it rolls this file in the same commit, moving everything under `## Unreleased` beneath a new `## <version> — <date>` heading (written even when the bucket is empty) and leaving `## Unreleased` first and empty. It refuses the sweep, with nothing published, when the roll would lie or it cannot read this file; when it skips allocation, nothing rolls. [`docs/RELEASE.md`](./docs/RELEASE.md), *Rolling `Unreleased` into a version*, says when each happens and what to do by hand. `test/docs/changelog_structure_test.rb` guards the shape.
4
4
 
5
5
  ## Unreleased
6
6
 
7
+ ## 0.133.1 — 2026-11-06
8
+
9
+ ### Changed
10
+
11
+ - **The browser lane runs as three shards.** It had grown to about 17 minutes of specs on
12
+ one runner, against about 9 minutes for the engine suite, so it was the long pole of
13
+ every engine PR. Each shard writes its own receipt, and `bin/e2e-executed-set-check`
14
+ now also refuses receipts whose shard total is not `shards:` in `config/e2e_lane.yml`.
15
+ Nothing changes for a consumer.
16
+
7
17
  ## 0.133.0 — 2026-11-06
8
18
 
9
19
  ### Deprecated
data/README.md CHANGED
@@ -2090,9 +2090,12 @@ in [`docs/RELEASE.md`](./docs/RELEASE.md).
2090
2090
 
2091
2091
  **Building an engine change?** Do **not** edit `lib/studio/version.rb`. The
2092
2092
  release owns the version, and McRitchie Studio's `bin/dor-check` refuses any PR
2093
- that touches that file. Update [`CHANGELOG.md`](./CHANGELOG.md) under
2094
- `Unreleased` (that is *not* gated), run `bin/release-check --build`, and open
2095
- your PR into `accepted`. That is the whole of your part.
2093
+ that touches that file. Do not edit [`CHANGELOG.md`](./CHANGELOG.md): add a
2094
+ fragment, `changelog.d/<slug>.<kind>.md` (format in
2095
+ [`changelog.d/README.md`](./changelog.d/README.md)). Engine CI runs
2096
+ `bin/changelog-check`, which fails a PR that changes what the gem ships and adds no
2097
+ fragment, or that adds lines under `## Unreleased`. Run `bin/release-check --build`
2098
+ and open your PR into `accepted`. That is the whole of your part.
2096
2099
 
2097
2100
  **Conducting the release?** Run `bin/release prepare` from mcritchie-studio and
2098
2101
  let it allocate the version — it derives the bump, commits `lib/studio/version.rb`
@@ -2100,8 +2103,9 @@ with its `Gemfile.lock` onto **`origin/release`**, then publishes, tags, and bum
2100
2103
  each consumer's lock. **Do not set the version by hand.** A hand-set number makes
2101
2104
  the allocation read the current version as already past the last tag and skip, so
2102
2105
  the hand number silently wins over the derived one, and the skip rolls no
2103
- changelog. **When it allocates, `prepare` also rolls
2104
- [`CHANGELOG.md`](./CHANGELOG.md)** in the same commit: everything under
2106
+ changelog. **When it allocates, the release compiles the fragments
2107
+ (`bin/changelog-compile`) and `prepare` rolls [`CHANGELOG.md`](./CHANGELOG.md)** in
2108
+ the same commit: everything under
2105
2109
  `## Unreleased` moves beneath the new version's heading, written even when the
2106
2110
  bucket is empty, and `## Unreleased` stays first and empty. It refuses the sweep,
2107
2111
  with nothing published, when the roll would lie or it cannot read the file.
@@ -1,3 +1,3 @@
1
1
  module Studio
2
- VERSION = "0.133.0"
2
+ VERSION = "0.133.1"
3
3
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: studio-engine
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.133.0
4
+ version: 0.133.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Alex McRitchie
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2026-11-06 00:00:00.000000000 Z
11
+ date: 2026-11-07 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: rails