studio-engine 0.32.0 → 0.32.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 +4 -4
- data/CHANGELOG.md +48 -1
- data/lib/studio/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: e04fa2a8f860281a68cd8534487c64308bc35b0e7fa36911e0b57b6a518be0fc
|
|
4
|
+
data.tar.gz: 774c6f65e6e08cd2204960973dea33f2e44c8e299d9683679dab6e9394e2dc8e
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: de4d5bcc12a5bc890655a3d49d7d88fdcf3e0a44de5951f0adbf7e6153eb146e93c6645600e642a7624ab74c8da5fed361f288a8b55b0c797603fdfd258eda8f
|
|
7
|
+
data.tar.gz: 761e8c0e87a81e9797164d44000c1e6e94dd2341bfbecf8ad7f60ef830c1f5e528f5fb09d6e73d502c13f420a9b06794c294440887d637b1df90e51840fe28a3
|
data/CHANGELOG.md
CHANGED
|
@@ -2,7 +2,53 @@
|
|
|
2
2
|
|
|
3
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 with `gem "studio-engine", "~> 0.6"`; bumping the gem version and updating consumer lockfiles is a release.
|
|
4
4
|
|
|
5
|
-
## 0.32.
|
|
5
|
+
## 0.32.1 — Unreleased
|
|
6
|
+
|
|
7
|
+
**Setup-guide corrections.** Docs only — no code, no behavior change.
|
|
8
|
+
|
|
9
|
+
### Docs
|
|
10
|
+
|
|
11
|
+
- **`NEW_APP_SETUP.md` § 15 "Lint And CI" — the two things a fresh app gets wrong
|
|
12
|
+
by default.** Both surface as a red CI lane on the app's first push and both
|
|
13
|
+
read like code defects when they aren't.
|
|
14
|
+
|
|
15
|
+
*Lint:* the generated `.rubocop.yml` inherits `rubocop-rails-omakase`, which
|
|
16
|
+
enforces `[ a, b ]`, while scaffolded code routinely writes `[a, b]` — so a new
|
|
17
|
+
app is usually born with a red `lint` lane. Run `bin/rubocop -a` before the
|
|
18
|
+
first commit, and either format to the cop or disable it deliberately. The
|
|
19
|
+
section tabulates which apps did which, stamped with the `origin/main` ref it
|
|
20
|
+
was surveyed at; that table lives in the guide rather than here because
|
|
21
|
+
`studio-engine.gemspec:21` packages this CHANGELOG but excludes `docs/`, so the
|
|
22
|
+
guide can be corrected without an erratum and this file cannot.
|
|
23
|
+
|
|
24
|
+
*CI:* the generated workflow installs a short fixed list and nothing else, so an
|
|
25
|
+
app that shells out to any other binary must add it to the install step in EVERY
|
|
26
|
+
test-running job. How many jobs that is depends on your Rails version — 8.1
|
|
27
|
+
generates separate `test` and `system-test` jobs with separate install steps,
|
|
28
|
+
7.2 a single job running both suites — and the guide tabulates both. The
|
|
29
|
+
failure is misleading: the test raises inside its own setup, so the lane reads
|
|
30
|
+
as a code defect rather than a missing package. moms-app's `BookStitcher` shells
|
|
31
|
+
out to `ffmpeg`, its README had listed `ffmpeg` as a requirement all along, and
|
|
32
|
+
the requirement was simply never told to CI.
|
|
33
|
+
- **`NEW_APP_SETUP.md` § 15 also covers the system-test lane that tests nothing.**
|
|
34
|
+
`rails new` wires a `test:system` CI invocation and the capybara/selenium gems,
|
|
35
|
+
and what you get behind it depends on your Rails version. On **7.2**
|
|
36
|
+
(`app_generator.rb:254-258`, called at `:459` under `depends_on_system_test?` —
|
|
37
|
+
true for a plain `rails new`) `test/system/.keep` and
|
|
38
|
+
`application_system_test_case.rb` are created, so the lane
|
|
39
|
+
runs, finds zero tests, and reports **GREEN** — a pass that means nothing. On
|
|
40
|
+
**8.1** (`:257-262`) that scaffolding sits behind a
|
|
41
|
+
`devcontainer? && depends_on_system_test?` guard, so a plain `rails new` gets the
|
|
42
|
+
invocation without the directory and the lane goes **RED** on
|
|
43
|
+
`cannot load such file -- test/system`. Either way the lane is not testing your
|
|
44
|
+
app; the green one is the harder to notice. The section tabulates where each
|
|
45
|
+
house app actually stands.
|
|
46
|
+
- **§ 16 Verify** no longer asks you to confirm a "yellow Development Environment
|
|
47
|
+
bar" — that hand-rolled strip was replaced by the shared environment banner in
|
|
48
|
+
0.30.0, so the checklist now names the banner, DEV MODE, and the Local Inbox link.
|
|
49
|
+
|
|
50
|
+
|
|
51
|
+
## 0.32.0 — 2026-08-09
|
|
6
52
|
|
|
7
53
|
**Readable ink on every theme, and the `btn-primary` label joins the token
|
|
8
54
|
contract.** (The token work merged after 0.31.0 was cut, so both land here.)
|
|
@@ -135,6 +181,7 @@ Do these two in this order; they do not commute.
|
|
|
135
181
|
`consume_magic_link` / `preview_magic_link` and overriding hooks. In
|
|
136
182
|
particular, move any `reset_session` into `sign_in_existing` only — the
|
|
137
183
|
`:continue` path must not reach it.
|
|
184
|
+
|
|
138
185
|
## 0.30.1 — 2026-08-08
|
|
139
186
|
|
|
140
187
|
**`NEW_APP_SETUP.md` § 5 gave a command that does not exist.** 0.30.0 documented
|
data/lib/studio/version.rb
CHANGED