@tdk-landscape/tdk-cli-core 1.3.66 → 1.3.68
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 +7 -0
- package/cli/dist/utils/resource-features.js +4 -1
- package/cli/package.json +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,13 @@ Notable changes to the `tdk` CLI. Versions match [npm](https://www.npmjs.com/pac
|
|
|
4
4
|
|
|
5
5
|
## Unreleased
|
|
6
6
|
|
|
7
|
+
## 1.3.67 (2026-09-28)
|
|
8
|
+
|
|
9
|
+
- The clean-machine quickstart run (`tdk project`, `tdk resource`, `tdk up`, wait for `/health`) now starts by itself after every successful release and tests exactly the version just published. It also still runs nightly and on demand.
|
|
10
|
+
- **`tdk resource --type backend` now produces a service whose image builds.** It set `featuresEnabled: ["prisma"]` by default but never created `prisma/schema.prisma` or the `prisma` dependency, so the generated Dockerfile failed on `COPY services/<stack>/<name>/prisma` and no scaffolded service could start. Prisma is now opt-in, like in the ERP and restaurant examples that boot, and `docs/FEATURES.md` says what it needs. Found by the clean-machine quickstart run, one step after the base-image race.
|
|
11
|
+
|
|
12
|
+
## 1.3.66 (2026-09-28)
|
|
13
|
+
|
|
7
14
|
- **`tdk up` on a machine with no base images no longer leaves every service stuck on a 404.** The generated Tiltfile dropped the golden-layers resource name, so app and migrator resources never waited for `golden-layers-build`. Their image builds started at once, failed with "pull access denied" because the base images did not exist yet, and Tilt never retried. Machines that had built the layers before (any second run) were unaffected, which hid it. Found by the clean-machine quickstart run.
|
|
8
15
|
- `tdk doctor` now names a missing golden base image for any project name (`shop-l4-backend`, ...). The hint was hard-coded to the `tdk-project-` prefix, so a real project got the raw BuildKit error.
|
|
9
16
|
|
|
@@ -42,7 +42,10 @@ export const RESOURCE_FEATURES = {
|
|
|
42
42
|
name: "prisma",
|
|
43
43
|
description: "Prisma CLI configuration for migrations and database client generation",
|
|
44
44
|
applies_to: ["backend", "worker", "migrator"],
|
|
45
|
-
|
|
45
|
+
// Opt-in: it needs a prisma/schema.prisma and the prisma dependency, which
|
|
46
|
+
// `tdk resource` does not create. Enabled by default it made every new
|
|
47
|
+
// backend's image build fail on `COPY .../prisma` and `test -f prisma/schema.prisma`.
|
|
48
|
+
enabled_by_default: false,
|
|
46
49
|
generator_file: "engine/topologies/tilt/generators/typescript/prisma_config.star",
|
|
47
50
|
output_file: ".autogenerated/prisma.config.autogenerated.ts",
|
|
48
51
|
},
|
package/cli/package.json
CHANGED
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tdk-landscape/tdk-cli-core",
|
|
3
|
-
"version": "1.3.
|
|
3
|
+
"version": "1.3.68",
|
|
4
4
|
"description": "Run 100 microservices on a 16 GB laptop without Kubernetes. Scaffold services and run them locally with hot reload, built on Tilt.",
|
|
5
5
|
"homepage": "https://tdk-landscape.github.io/tdk-website",
|
|
6
6
|
"repository": {
|