Release 2.0

[thesayyn]

It's been almost a year since we released the 1.0, and now it's time for us to make breaking changes we have been holding back for more than 6 months.

Breaking changes that we are planning.

• Under consideration: drop zot as a registry toolchain and only support crane registry
• Drop curl fallback for oci_pull, now that feat: add support for arbitrary headers rctx.download[_and_extract] bazelbuild/bazel#19501 is fixed.
• Drop bazel 5 altogether.
• Drop yq as a dependency.
• Start using bsdtar toolchain from bazel-lib for hermeticity.
• Upgrade bazel-lib to 2.0

[alexeagle]

Target date ought to be about a year from 1.0.0, so that's not until May, plenty of time for some Beta releases and a long RC period.

We'll have to drop support for Bazel <7.1 for users who need custom headers, though I guess we can still say Bazel 6 and Bazel 7.0 are good enough if you weren't relying on the curl fallback.

[thesayyn]

We are also designing a registryless version of rules_oci 2.0 which will be significantly faster compared to the current design.

[siddharthab]

registryless version of rules_oci 2.0

This will be very appreciated. Our (bioinformatics/ML) images tend to be very big, and moving from rules_docker to rules_oci, the registry roundabout was the most significant pain we felt.

[thesayyn]

Design doc for 2.0 redesign of OCI Image is here: https://docs.google.com/document/d/1wZEB9QFxyrydhLiafYbaJ0D7Jd2FZRZjvoTtx0B8-yY

[thesayyn]

As of today everything in the list above is done.