Change Module Name To Github Oras Project Oras Go V3 Issue 483 As a solution, it is better to rename the module name under github for better stability and availability. since this is a breaking change, the change should happen for the next generation of oras go. that is, oras go v3. the module name will be github oras project oras go v3. It is better rename it to github oras project oras so that changes to oras.land website will not impact oras. the module name renaming will not impact real users since the oras is a cli and is not supposed to be referenced as a go module.
Github Oras Project Oras Go Oras Go Library Oras go is a go library for managing oci artifacts, compliant with the oci image format specification and the oci distribution specification. it provides unified apis for pushing, pulling, and managing artifacts across oci compliant registries, local file systems, and in memory stores. I've made some changes locally and have updated the local go.mod to be v4 instead of v3 but this now causes the running of the tests locally to fail (see below, i've genericized the output). We should rename the go module from oras.land oras credentials go to github oras project oras credentials go. While this change does not affect the public api of oras go v1, it may cause issues for users who are using oras go v1 along with older versions of docker docker (see #527).
Pull Requests Oras Project Oras Credentials Go Github We should rename the go module from oras.land oras credentials go to github oras project oras credentials go. While this change does not affect the public api of oras go v1, it may cause issues for users who are using oras go v1 along with older versions of docker docker (see #527). While we already have documentation covering the general concepts of oras on oras.land and detailed api specifications available on pkg.go.dev, users may still encounter challenges when trying to use oras go v2 in their projects. The package github oras project oras go pkg oras can quickly be imported in other go based tools that wish to benefit from the ability to store arbitrary content in container registries. Documentation for the oras go library is located on the project website: oras.land client libraries go. this project has adopted the cncf code of conduct. see code of conduct.md for further details. Global access might not be granted for an entire registry. instead, multiple service accounts robots may be used for narrowly scoped push pull actions. registry authentication should be done from most specific to least specific.
Update Oras Pack To Comply With Image Spec V1 1 0 Rc4 Issue 532 While we already have documentation covering the general concepts of oras on oras.land and detailed api specifications available on pkg.go.dev, users may still encounter challenges when trying to use oras go v2 in their projects. The package github oras project oras go pkg oras can quickly be imported in other go based tools that wish to benefit from the ability to store arbitrary content in container registries. Documentation for the oras go library is located on the project website: oras.land client libraries go. this project has adopted the cncf code of conduct. see code of conduct.md for further details. Global access might not be granted for an entire registry. instead, multiple service accounts robots may be used for narrowly scoped push pull actions. registry authentication should be done from most specific to least specific.
Comments are closed.