You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: changes.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,9 @@
1
1
# Changes
2
2
3
+
### 0.13.0
4
+
5
+
- Allow repo-owned manifests to satisfy config contract coverage when they declare explicit config contract metadata or runtime config sections, avoiding forced `.env.example` files for repos with custom manifest contracts.
6
+
3
7
### 0.12.0
4
8
5
9
- Add generator source refs to `.rabbit/context.yaml` so generated context points to the dev.kit homepage, source repo, npm package, and installation guide.
Copy file name to clipboardExpand all lines: docs/context-coverage.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@ gaps:
79
79
message: No explicit configuration contract was detected.
80
80
```
81
81
82
-
That should lead to a repo change such as adding config docs, manifest metadata, or a checked-in example file, then regenerating context.
82
+
That should lead to a repo change such as adding config docs, adding explicit manifest metadata, declaring runtime config sections in a repo-owned manifest, or adding a checked-in example file, then regenerating context.
Copy file name to clipboardExpand all lines: docs/references/config-contract-surfaces.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Configuration is often declared through:
11
11
-`.env.example`, `.env.sample`, or `.env.template`
12
12
- focused repo docs such as `README.md` or `docs/config.md`
13
13
- deploy manifests such as `deploy.yml`
14
-
- versioned YAML/JSON manifests with explicit config metadata
14
+
- versioned YAML/JSON manifests with explicit config metadata or runtime config sections
15
15
- checked-in example config files when the repo uses a custom format
16
16
17
17
## Build defaults and runtime overlays
@@ -26,6 +26,8 @@ Example pattern:
26
26
27
27
That is still one coherent repo contract as long as the split is explicit and checked in.
28
28
29
+
Custom manifests should not rely on filename rules. For YAML manifests, `dev.kit` treats explicit contract metadata such as `contract: config` or runtime config sections such as `config.env`, `config.environment`, `config.image`, `config.command`, or top-level `env`/`variables`/`settings` as configuration contract evidence.
0 commit comments