Skip to content

docs: target 0.103.0 in version notes - #1415

Merged
LalatenduMohanty merged 1 commit into
python-wheel-build:new-resolver-configfrom
LalatenduMohanty:docs-version-0.103.0
Oct 30, 2026
Merged

LalatenduMohanty merged 1 commit into
python-wheel-build:new-resolver-configfrom
LalatenduMohanty:docs-version-0.103.0

Conversation

@LalatenduMohanty

Copy link
Copy Markdown
Member

0.102.0 was released from main without 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.

  • Every versionadded and versionchanged added on this branch (0.95.0, 0.96.0 and 0.102.0) now says 0.103.0. Notes that already exist on main are not touched.
  • Notes that now sit next to each other with the same version are merged.
  • Removed the stale "do not fall back to PyPI" sentence for hook profiles. Since feat(resolver): let hook profiles work with only a download hook #1409, a hook profile without a get_resolver_provider hook finds versions on its index_url.

Docs only. hatch run docs:build (warnings as errors) and hatch run lint:check pass.

🤖 Generated with Claude Code

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>
@LalatenduMohanty
LalatenduMohanty requested a review from a team as a code owner October 30, 2026 15:25
@coderabbitai

coderabbitai Bot commented Oct 30, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@LalatenduMohanty

Copy link
Copy Markdown
Member Author

It can't be a direct commit on #1414: the branch rules require a PR into new-resolver-config. Once #1415 merges, it shows up in #1414 automatically.

@rd4398 rd4398 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mergify

mergify Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

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.

@LalatenduMohanty
LalatenduMohanty merged commit 5103e8b into python-wheel-build:new-resolver-config Oct 30, 2026
37 of 38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants