Release 2.0

[rickeylev]

Tracking issue for the 2.0 release

2.0 breaking changes

There are 5 changes we expect to be disruptive:

1. On Windows symlinks are required. Add startup --windows_enable_symlinks to your .bazelrc and enable Windows developer mode
2. Windows: lite venvs are created for binaries/tests
3. Windows and --build_python_zip: The --build_python_zip flag is ignored. Use the py_zipapp_* rules instead.
4. For cross-building using pip.parse.experimental_index_url: you must now explicitly list the desired cross-built platforms using pip.parse.target_platforms
5. When searching for packages in indexes the one specified with --index-url will be searched after the ones specified via --extra-index-url when using the bazel downloader.

See the 2.0.0 changelog for more information

rc0

• Update change log, version markers chore: update changelog, version markers, for 2.0 release #3689
• Enable experimental_index_url by default feat!(pypi): enable bazel downloader by default #3691
• Create 2.0 branch
• backport chore: populate 2.0 for VERSION_NEXT_FEATURE for py_wheel add_path_prefix #3703
• Tag 2.0.0-rc0

rc1

• Backport fix(sphinxdocs): update MODULE.bazel to depend on a released version #3704
• Backport chore: have no-matching-distribution error message hint about target_platforms vs requirements_by_platform #3701
• Tag 2.0.0-rc1

rc2

• backport sphinxdocs: remove local rules_python dev overrides #3705
• tag 2.0.0-rc2

rc3

• backport fix(pypi): skip index lookups when all package overrides are specified #3710
• backport fix(pypi): correctly write the used facts back #3719
• backport fix(pypi): build the environment on the fly #3720
• Tag 2.0.0-rc3

rc4

• backport fix(pypi): don't resolve python interpreter when not necessary #3727
• Tag 2.0.0-rc4

Final release

• Tag 2.0 final

[aignas]

I'd like to enable experimental index url by default in that release, so let me see if I can do something tomorrow. It should be a reasonably small change, so the diff won't be too invasive.

[aignas]

PTAL: #3691

[rickeylev]

3691 Approved and queued for merged

[rickeylev]

2.0 branch created.

@aignas did you want to block release on the bug reported in slack? If so, how long? https://bazelbuild.slack.com/archives/CA306CEV6/p1775853239774449

[aignas]

I am not sure if it is a bug, I'm OK to release rc0.

[rickeylev]

2.0.0-rc0 tagged, pending BCR: bazelbuild/bazel-central-registry#8401

[aignas]

Maybe we should backport the error message pr #3701. But let's see if we hear more from people.

[aignas]

It seems that we'll need to set a non-zero version for sphinxdocs.

[rickeylev]

Backported 3704 and 3701. rc1 tagged

[rickeylev]

Looks like there's another issue with the sphinxdocs bcr config. I'll have a look tonight.

[rickeylev]

2.0.0-rc2 tagged, bcr: bazelbuild/bazel-central-registry#8421 (review)

[kberezin-nshl]

Hey, just wondering, is there any ETA for the final release to BCR?
(Or at least to merge an existing rc2 BCR PR which is ready, but lacking approvals)

We're particularly interested in getting this fix