Skip to content

fix(auth): restore netrc authentication for unregistered hosts - #1461

Open
Allda wants to merge 2 commits into
python-wheel-build:mainfrom
Allda:fix/netrc-auth-fallback
Open

Allda wants to merge 2 commits into
python-wheel-build:mainfrom
Allda:fix/netrc-auth-fallback

fix(auth): enforce netrc authentication policy on redirects

a07cb2f
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 20, 2026 in 2s

1 rule matches and 3 potential rules

✅ Rule: Add CI label (label)

  • any of:
    • files~=pyproject.toml
    • files~=tests/
    • files~=.github/
    • files~=.mdformat.toml
    • files~=e2e/
    • title~=^ci:
    • title~=^e2e:
    • title~=^hatch:

Rule: Add Mergify label (label)

  • any of:
    • files~=.mergify.yml$
    • title~=^mergify:

Rule: Automatic merge on approval (queue)

  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rule default]
      • #approved-reviews-by>=1
      • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
      • github-code-owner-review-satisfied [🛡 GitHub repository ruleset rule main]
      • github-review-approved [🛡 GitHub branch protection]
      • github-review-approved [🛡 GitHub repository ruleset rule main]
      • any of:
        • all of:
          • check-success=e2e (3.12, 1.75, ci_bootstrap_parallel_suite, ubuntu-latest)
          • check-success=e2e (3.12, 1.75, ci_bootstrap_suite, ubuntu-latest)
          • check-success=e2e (3.12, 1.75, ci_build_suite, ubuntu-latest)
          • check-success=e2e (3.12, 1.75, ci_config_suite, ubuntu-latest)
          • check-success=e2e (3.12, 1.75, ci_specialized_suite, ubuntu-latest)
          • check-success=e2e (3.12, 1.75, ci_workflow_suite, ubuntu-latest)
          • check-success=e2e (3.13, 1.75, ci_bootstrap_parallel_suite, ubuntu-latest)
          • check-success=e2e (3.13, 1.75, ci_bootstrap_suite, ubuntu-latest)
          • check-success=e2e (3.13, 1.75, ci_build_suite, ubuntu-latest)
          • check-success=e2e (3.13, 1.75, ci_config_suite, ubuntu-latest)
          • check-success=e2e (3.13, 1.75, ci_specialized_suite, ubuntu-latest)
          • check-success=e2e (3.13, 1.75, ci_workflow_suite, ubuntu-latest)
          • check-success=e2e (3.14, 1.75, ci_bootstrap_parallel_suite, ubuntu-latest)
          • check-success=e2e (3.14, 1.75, ci_bootstrap_suite, ubuntu-latest)
          • check-success=e2e (3.14, 1.75, ci_build_suite, ubuntu-latest)
          • check-success=e2e (3.14, 1.75, ci_config_suite, ubuntu-latest)
          • check-success=e2e (3.14, 1.75, ci_specialized_suite, ubuntu-latest)
          • check-success=e2e (3.14, 1.75, ci_workflow_suite, ubuntu-latest)
          • check-success=pkglint
          • check-success=pre-commit
          • check-success=readthedocs
          • check-success=unit (3.12, 1.75, ubuntu-latest)
          • check-success=unit (3.13, 1.75, ubuntu-latest)
          • check-success=unit (3.14, 1.75, macos-latest)
          • check-success=unit (3.14, 1.75, ubuntu-latest)
        • all of:
          • -files~=^(?!docs/)(?![^/]+\.(md|rst)$)(?!LICENSE$)
          • check-success=pkglint
          • check-success=pre-commit
          • check-success=readthedocs
      • -draft
      • any of:
        • -files~=^\.github/workflows/
        • head-repo-full-name=python-wheel-build/fromager
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = @mergify/Configuration changed
    • check-success = @mergify/Configuration has been deleted

Rule: Ping author on conflicts (comment)

  • conflict
  • -closed

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com