@yanlinglabs/winter-provider-catalog 0.0.17 → 0.0.22
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/NOTICE +41 -59
- package/PROVENANCE.md +52 -7
- package/README.md +7 -1
- package/dist/extract/merge.d.ts +11 -3
- package/dist/index.d.ts +1 -0
- package/dist/index.js +26970 -13393
- package/dist/tag-renames.d.ts +9 -0
- package/generated/catalog.json +10274 -2515
- package/generated/rejections.json +11 -3
- package/generated/upstream-layer.json +13 -79
- package/overlay/families.json +91 -7
- package/overlay/models.json +7312 -1946
- package/overlay/pricing.json +243 -0
- package/overlay/providers.json +187 -5
- package/package.json +1 -1
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Old compound `<providerId>/<id>` tag -> the catalog key it now lives under.
|
|
3
|
+
*
|
|
4
|
+
* Every value names a real row of the bundled catalog; no key is ever a live catalog key itself (a
|
|
5
|
+
* rename never shadows a tag that still resolves on its own). `canonicalModelTag` (the daemon, WS-21
|
|
6
|
+
* spec §8 step 5) applies this at every stored-tag read boundary, so a tag written by an older
|
|
7
|
+
* catalog keeps resolving after a refresh renames the row underneath it.
|
|
8
|
+
*/
|
|
9
|
+
export declare const CATALOG_TAG_RENAMES: Readonly<Record<string, string>>;
|