In order to work on taskcluster-client updates for RFC 0128, we need a (staging) deployment of taskcluster that declares a coherent set of manifest/references/schemas using the new file formats. The latest staging deployments have yet to use the new syntax. Notably, some manifests are missing (such as [manifest-v3.json](https://taskcluster-staging.net/schemas/common/manifest-v3.json)), and [the service manifest](https://taskcluster-staging.net/references/manifest.json) is still using `manifest-v2.json` format.
Bug 1519867 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In order to work on taskcluster-client updates for RFC 0128, we need a (staging) deployment of taskcluster that declares a coherent set of manifest/references/schemas using the new file formats. The latest staging deployments have yet to use the new syntax. Notably, some manifests are missing (such as [manifest-v3.json](https://taskcluster-staging.net/schemas/common/manifest-v3.json)), and [the service manifest](https://taskcluster-staging.net/references/manifest.json) is still using `manifest-v2.json` format rather than `manifest-v3.json`.
In order to work on taskcluster-client updates for [RFC 0128](https://github.com/taskcluster/taskcluster-rfcs/blob/master/rfcs/0128-redeployable-clients.md), we need a (staging) deployment of taskcluster that declares a coherent set of manifest/references/schemas using the new file formats. The latest staging deployments have yet to use the new syntax. Notably, some manifests are missing (such as [manifest-v3.json](https://taskcluster-staging.net/schemas/common/manifest-v3.json)), and [the service manifest](https://taskcluster-staging.net/references/manifest.json) is still using `manifest-v2.json` format rather than `manifest-v3.json`.