modelcontextprotocol/registry
Watch
1
0
Fork
You've already forked registry
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Clean up schema by simplifying version structure (#379)

Browse source 
## Summary

Simplified the schema structure by:
- Replacing `version_detail.version` with direct `version` field  
- Removing unused `release_date` field from seed data
- Updating all API types, models, and tests to match new structure
- Maintaining backwards compatibility in API responses

This change makes the schema more intuitive and reduces nesting depth.
This commit is contained in:
adam jones 2025-09-08 14:32:59 -07:00 • committed by GitHub
commit f975e68cf2
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 540 additions and 1973 deletions
Download patch file Download diff file Expand all files Collapse all files

32
docs/explanations/versioning.md
View file

@ -19,9 +19,7 @@ Server authors SHOULD use [semantic versions](https://semver.org/) following the
```json
{
"version_detail": {
"version": "1.2.3"
}
"version": "1.2.3"
}
```
@ -30,9 +28,7 @@ Server authors SHOULD use versions aligned with their underlying packages to red
```json
{
"version_detail": {
"version": "1.2.3"
},
"version": "1.2.3",
"packages": [{
"registry_name": "npm",
"name": "@myorg/my-server",
@ -46,9 +42,7 @@ If server authors expect to have multiple registry versions for the same package
```json
{
"version_detail": {
"version": "1.2.3-1"
},
"version": "1.2.3-1",
"packages": [{
"registry_name": "npm",
"name": "@myorg/my-server",
@ -111,9 +105,7 @@ Registry clients SHOULD:
### Alignment Examples
```json
{
"version_detail": {
"version": "1.2.3-1"
},
"version": "1.2.3-1",
"packages": [{
"registry_name": "npm",
"name": "@myorg/k8s-server",
@ -136,9 +128,7 @@ Existing servers with non-semantic versions will continue to work without change
**Package and server versions aligned**:
```json
{
"version_detail": {
"version": "1.2.3"
},
"version": "1.2.3",
"packages": [
{
"registry_type": "npm",
@ -153,9 +143,7 @@ Existing servers with non-semantic versions will continue to work without change
**Server metadata changes without package updates**:
```json
{
"version_detail": {
"version": "1.2.3-1"
},
"version": "1.2.3-1",
"packages": [
{
"registry_type": "npm",
@ -172,9 +160,7 @@ Note: `1.2.3-1` is considered lower than `1.2.3` in semver ordering. Publish pre
**Remote servers without package dependencies**:
```json
{
"version_detail": {
"version": "2.1.0"
},
"version": "2.1.0",
"remotes": [
{
"transport_type": "sse",
@ -193,9 +179,7 @@ Version strategy options:
**Different package versions**:
```json
{
"version_detail": {
"version": "1.3.0"
},
"version": "1.3.0",
"packages": [
{
"registry_type": "npm",