Repository navigation
docs: target 0.103.0 in version notes - #1415
LalatenduMohanty merged 1 commit into
Conversation
0.102.0 was released from `main` without the new resolver config, so the feature branch's version notes must name the next release. - Change every `versionadded` and `versionchanged` added on this branch (0.95.0, 0.96.0 and 0.102.0) to 0.103.0. - Merge notes that now sit next to each other with the same version. - Drop the stale "do not fall back to PyPI" sentence for hook profiles. Since python-wheel-build#1409, a hook profile without a `get_resolver_provider` hook finds versions on its `index_url`. Co-Authored-By: Claude <claude@anthropic.com> Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
5103e8b
into
python-wheel-build:new-resolver-config
0.102.0 was released from
mainwithout the new resolver config. This updates the branch's version notes so they name the next release, 0.103.0. Part of #1254; it will show up in #1414 once merged.versionaddedandversionchangedadded on this branch (0.95.0, 0.96.0 and 0.102.0) now says 0.103.0. Notes that already exist onmainare not touched.get_resolver_providerhook finds versions on itsindex_url.Docs only.
hatch run docs:build(warnings as errors) andhatch run lint:checkpass.🤖 Generated with Claude Code