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: specification.md
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,6 +133,14 @@ $ manager config get registries
133
133
]
134
134
```
135
135
136
+
#### Registry versioning (optional)
137
+
138
+
Registries can expose versioned endpoints to avoid breaking changes when introducing new features. When a registry is versioned, managers should append the version segment to the registry root when requesting resources.
139
+
140
+
Example: Registry root `https://example.com/registry` with version `v1` → fetch plugin list at `https://example.com/registry/v1/plugins`.
141
+
142
+
Versioning is optional — if Managers call the root url, they will get the latest version by default.
143
+
136
144
### App directory
137
145
138
146
Defaults to manager installation directory.
@@ -437,13 +445,15 @@ Create new package metadata:
437
445
- If package version not found return error
438
446
- Check to see if package is installed:
439
447
- If not installed, return error
440
-
- Filter package files that match the current architecture and system
441
-
- Find a file with an `open` field defined:
442
-
- If no compatible file with `open` field found, return error
443
-
- Execute the file/command specified in the file's `open` field with any additional options
448
+
- Filter package `files` entries that match the current architecture and system
449
+
- Find a `files` entry that includes an `open` field and matches the system/architecture:
450
+
- If no compatible `files` entry with an `open` field is found, return error
451
+
- Execute the file/command specified in that `files` entry's `open` field.
452
+
453
+
Note: The manager will use the `open` field defined in the package metadata (per-file) to determine the correct entry point for the target system.
444
454
445
455
Open any package by slug and version:
446
-
`$ manager <registryType> open <slug>@<version> <options>`
0 commit comments