@radhya/mach 2.6.8 → 2.6.9
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/dist/index.js +136 -136
- package/docs/deep-links.md +6 -0
- package/package.json +1 -1
package/docs/deep-links.md
CHANGED
|
@@ -88,6 +88,12 @@ to `dist` or `build/web` while deep-link setup wrote files under `public` or
|
|
|
88
88
|
`deep-links`. The generated files replace stale association files in the upload,
|
|
89
89
|
so the hosted release matches `mach.config.json`.
|
|
90
90
|
|
|
91
|
+
Before upload, Mach verifies that the generated AASA and Asset Links files
|
|
92
|
+
match the app IDs in the active `mach.config.json`. When Mach can identify the
|
|
93
|
+
selected hosting project's stable Production hostname, it also blocks a deploy
|
|
94
|
+
whose deep-link domain belongs to another app. This prevents a root workspace
|
|
95
|
+
config from silently publishing one product's AASA to another product's host.
|
|
96
|
+
|
|
91
97
|
`mach.config.json` is the only Mach deep-link source of truth. Values already available from the selected profile or root config are not duplicated inside `deepLinks`. A typical generated block is intentionally small:
|
|
92
98
|
|
|
93
99
|
```json
|