f6db8c5f8709 → bd17546f47b8 · 1338 changes across 215 operations
- GET/api/papers/{paperId}
- ▲
the response property
///became nullable for the status - ▲
added
subschema #1subschema #2to the//response propertyoneOflist for the response status - ▲
added
subschema #1subschema #2to the////response propertyoneOflist for the response status - ▲
added
subschema #1subschema #2to the//response propertyoneOflist for the response status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
////response's property type changed from no type tostringfor status
- ▲
- GET/api/whoami-v2
- ▲
the response property
/became nullable for the status - ▲
the response property
///became nullable for the status - ▲
the response property
///became nullable for the status - ▲
the response property
/became nullable for the status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status
- ▲
- GET/api/datasets/{namespace}/{repo}/tree/{rev}/{path}
- ▲
for the
queryrequest parameterexpand, default valuefalsewas removed - ▲
for the
queryrequest parameterrecursive, default valuefalsewas removed - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status
- ▲
- GET/api/models/{namespace}/{repo}/tree/{rev}/{path}
- ▲
for the
queryrequest parameterexpand, default valuefalsewas removed - ▲
for the
queryrequest parameterrecursive, default valuefalsewas removed - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status
- ▲
- GET/api/spaces/{namespace}/{repo}/tree/{rev}/{path}
- ▲
for the
queryrequest parameterexpand, default valuefalsewas removed - ▲
for the
queryrequest parameterrecursive, default valuefalsewas removed - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status
- ▲
- POST/api/datasets/{namespace}/{repo}/paths-info/{rev}
- ▲
the
/request property type changed from no type tostring - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status
- ▲
- POST/api/models/{namespace}/{repo}/paths-info/{rev}
- ▲
the
/request property type changed from no type tostring - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status
- ▲
- POST/api/spaces/{namespace}/{repo}/paths-info/{rev}
- ▲
the
/request property type changed from no type tostring - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/////response's property type changed from no type tostringfor status
- ▲
- POST/api/settings/webhooks/{webhookId}
- ▲
the
/request property type changed from no type tostring - ▲
the
request property type changed fromobjectto no type - ▲
the
//request property type changed from no type tostring - ▲
added
subschema #1subschema #2to the/response propertyoneOflist for the response status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
/response's property type changed fromobjectto no type for status - ▲
the
///response's property type changed from no type tostringfor status
- ▲
- POST/api/settings/webhooks
- ▲
the
/request property type changed from no type tostring - ▲
the
request property type changed fromobjectto no type - ▲
the
//request property type changed from no type tostring - ▲
added
subschema #1subschema #2to the/response propertyoneOflist for the response status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
/response's property type changed fromobjectto no type for status - ▲
the
///response's property type changed from no type tostringfor status
- ▲
- POST/api/quicksearch
- ▲
for the
queryrequest parameterincludeInvitees, default valuefalsewas removed - ▲
for the
queryrequest parameterincludeInvitees, the type changed from no type tobooleanstring - ▲
removed
subschema #1subschema #2from therequest propertyanyOflist - ▲
the
request property type changed from no type tobooleanstring - ▲
the
/request property type changed from no type tostring - ▲
the
/request property type changed from no type tostring - ▲
the
//request property type changed from no type tostring - ▲
the
//request property type changed from no type tostring
- ▲
- POST/api/jobs/{namespace}
- ▲
the request's body type changed from
objectto no type - ▲
the response property
/became nullable for the status - ▲
added
subschema #1subschema #2subschema #3subschema #4to theresponse propertyoneOflist for the response status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status
- ▲
- POST/api/scheduled-jobs/{namespace}/{jobId}/run
- ▲
the response property
/became nullable for the status - ▲
added
subschema #1subschema #2subschema #3subschema #4to theresponse propertyoneOflist for the response status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status
- ▲
- POST/api/jobs/{namespace}/{jobId}/cancel
- ▲
the response property
/became nullable for the status - ▲
added
subschema #1subschema #2subschema #3subschema #4to theresponse propertyoneOflist for the response status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status
- ▲
- POST/api/jobs/{namespace}/{jobId}/duplicate
- ▲
the response property
/became nullable for the status - ▲
added
subschema #1subschema #2subschema #3subschema #4to theresponse propertyoneOflist for the response status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status
- ▲
- PUT/api/jobs/{namespace}/{jobId}/expose
- ▲
the response property
/became nullable for the status - ▲
added
subschema #1subschema #2subschema #3subschema #4to theresponse propertyoneOflist for the response status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status
- ▲
- GET/api/jobs/{namespace}/{jobId}
- ▲
the response property
/became nullable for the status - ▲
added
subschema #1subschema #2subschema #3subschema #4to theresponse propertyoneOflist for the response status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status
- ▲
- PUT/api/jobs/{namespace}/{jobId}/labels
- ▲
the response property
/became nullable for the status - ▲
added
subschema #1subschema #2subschema #3subschema #4to theresponse propertyoneOflist for the response status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status
- ▲
- GET/api/jobs/{namespace}
- ▲
the response property
//became nullable for the status - ▲
added
subschema #1subschema #2subschema #3subschema #4to the/response propertyoneOflist for the response status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
//response's property type changed from no type tostringfor status
- ▲
- GET/api/organizations/{name}/billing/usage
- ▲
the response property
///became nullable for the status - ▲
the response property
///became nullable for the status - ▲
added
subschema #1subschema #2to the/response propertyoneOflist for the response status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status - ▲
the
///response's property type changed from no type tostringfor status - ▲
the
/response's property type changed from no type tostringfor status
- ▲