@shivaedev/create-app 0.13.2 → 0.15.0

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.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,57 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.15.0 - 2026-10-25
4
+
5
+ ### Added
6
+
7
+ - effect-sql records the database release after successful migrations and coordinates worker drain with typed PostgreSQL heartbeat rows.
8
+ - effect-pg-boss pauses fetching while the database belongs to another release, finishes active jobs, and resumes when its release owns the database again.
9
+ - Platform migration options accept an optional `release` for deployment migration and worker readiness.
10
+ - Generated workers step aside for a newer release and drain on SIGTERM, with queue expiry, stop timeout and Railway draining configured together.
11
+
12
+ ## 0.14.1 - 2026-10-25
13
+
14
+ ### Added
15
+
16
+ - `queryRoute` supplies TanStack Router query loaders and search dependencies, mapping `NotFound` rejections to the route's not-found component.
17
+ - `@shivaedev/platform`: `authDatabase` accepts optional `max` and `application_name` pool settings.
18
+
19
+ ### Changed
20
+
21
+ - Generated starter notes routes use query loaders and show a not-found screen for missing notes, with a link back to the list.
22
+ - `@shivaedev/create-app`: Starter stories run the web host and worker with test-sized SQL, authentication and jobs pools.
23
+
24
+ ## 0.14.0 - 2026-10-25
25
+
26
+ ### Added
27
+
28
+ - `@shivaedev/effect-sql` exports `pendingPostgresMigrations` to read pending ledger migration IDs and names and schema component names and details.
29
+ - `@shivaedev/platform` logs migration wait start, periodic progress, completion and timeout through Effect's logger with pending migration and component annotations. `migrations.progressInterval` controls progress logging independently of polling and defaults to 30 seconds.
30
+ - Generate the starter foundation without the notes example with `create-app <folder> --minimal`; starter updates preserve the minimal choice.
31
+ - Generated apps record and lower Quality debt with `pnpm baseline write --rule <id>`, `pnpm baseline tighten` and `pnpm baseline prune`, with guidance on when to use each command.
32
+
33
+ ### Changed
34
+
35
+ - `@shivaedev/create-app`'s starter worker uses the host's migration wait logs and keeps its job readiness line.
36
+
37
+ ## 0.13.5 - 2026-10-25
38
+
39
+ ### Changed
40
+
41
+ - Release with updated workspace dependencies.
42
+
43
+ ## 0.13.4 - 2026-10-25
44
+
45
+ ### Changed
46
+
47
+ - Generated apps use the latest released starter dependencies.
48
+
49
+ ## 0.13.3 - 2026-10-25
50
+
51
+ ### Changed
52
+
53
+ - Release with updated workspace dependencies.
54
+
3
55
  ## 0.13.2 - 2026-10-25
4
56
 
5
57
  ### Changed
package/README.md CHANGED
@@ -22,6 +22,8 @@ Next steps:
22
22
 
23
23
  Use Node 24 or newer and pnpm. The package contains a snapshot of the starter made when it is packed. Platform dependencies use exact versions from the starter's `published-versions.json`; its self-contained pnpm catalog pins the remaining dependencies.
24
24
 
25
+ Pass `--minimal` to start with the foundation alone: the same starter without the notes module or its client, server, worker and migration registrations. The default includes the notes example. Starter updates preserve the minimal choice.
26
+
25
27
  The folder argument may include a parent path. Its final folder name becomes the package name and must be a lowercase npm name. The destination must be absent or empty, including hidden files. The command runs `pnpm run setup` in the generated app to install dependencies and Quality's pre-commit hook, and reports setup failure with a nonzero exit status. Setup installs the hook only when the app has its own `.git`; it leaves an enclosing repository's hooks alone.
26
28
 
27
29
  The command writes a git-ignored `.env.local` with a fresh authentication secret and local development and test database URLs. Existing files are never overwritten. Database names replace dots and hyphens in the app name with underscores, prefix a name starting with a digit with `app_`, and limit the stem to 58 characters before adding `_dev` and `_test`.