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
{{ message }}
This repository has been archived by the owner on May 15, 2024. It is now read-only.
The PR describing the OCI Artifact Manifest spec has been merged. The schema described in the PR seems to be the same as the ORAS Artifact spec. How will the two be reconciled? Will the ORAS Artifact spec be dropped in favor of the standard? Will the oras cli be implemented with the new OCI Artifact spec?
The text was updated successfully, but these errors were encountered:
There is a little background about these two PRs in this blog. In short, you can follow the OCI Artifact spec as the main because it originated from the ORAS artifacts spec.
Will the ORAS Artifact spec be dropped in favor of the standard?
Eventually yes. But now it is still maintained by the ORAS community. It might not have new major updates on it.
ORAS artifact spec is still consumed by some registries and dependents now, so we need to leave some time to wait for them to use the new version of ORAS with OCI artifact manifest support and migrate to OCI artifact manifest. After that period, this repo will eventually be archived, the ORAS artifact spec will have its mission completed.
Will the oras cli be implemented with the new OCI Artifact spec?
Yes, ORAS CLI has fully supported the OCI artifact spec in v0.16 last week. You can find the release notes for details.
The PR describing the OCI Artifact Manifest spec has been merged. The schema described in the PR seems to be the same as the ORAS Artifact spec. How will the two be reconciled? Will the ORAS Artifact spec be dropped in favor of the standard? Will the oras cli be implemented with the new OCI Artifact spec?
The text was updated successfully, but these errors were encountered: