-
Currently Nomad release tags cover only the server module at `github.com/hashicorp/nomad`. The submodule containing client API `github.com/hashicorp/nomad/api` is not versioned, which leads to applica…
-
[Bug 1051056](https://bugzilla.mozilla.org/show_bug.cgi?id=1051056), Bugzilla 6.0
-
Hello,
I am trying to create a new version of a resource through the API without success.
I tried to `PUT` the same resource incrementing the `versionNumber` and passing the same `vuid` but th…
-
cloudresourcemanager v1 and v2 have different functionality. A user is unable to use both as they share an artifact name and differ only on versions.
We should be able to pack all the generated ver…
-
We have a link version checker set up in CI to make sure that links in `api_versioned_docs` are pointing to the appropriate timestamped versions of the `risc0` repo.
We [recently realized](https://g…
-
`ServiceServingCertSignerConfig` embeds `metav1.TypeMeta` and `configv1.GenericControllerConfig`: https://github.com/openshift/api/blob/master/servicecertsigner/v1alpha1/types.go#L15-L21
At the tim…
-
I'm working with a versioned api calling and rendering the Swagger documentation with get_swagger_view
```
url(r'^api/swagger/', get_swagger_view(title='SEED API'), name='swagger'),
```
I can se…
-
It would be nice if our docs were versioned so that users could navigate directly to the `1.8` docs. This may make sense initially just for API Docs (each of which versions independently).
-
This is something we could do, if we backport the needed pieces from #165, and figure out a way to robustly keep both 11.8.x and 12.x docs updated (make the docs rebuildable as needed).
-
Currently, the JSON-RPC server is versioned via semver and exposed via the [`version`](https://github.com/decred/dcrd/blob/master/docs/json_rpc_api.mediawiki#version) JSON-RPC method. While this appr…