Bump gojiplus/py-canon/.github/workflows/reusable-ci.yml from 07c6621880b82afd28ab7230eab6e79f96d080e3 to b17ef8a96fb6afe3003d38cdec83afabe3ec9111

[dependabot]

Bumps gojiplus/py-canon/.github/workflows/reusable-ci.yml from 07c6621880b82afd28ab7230eab6e79f96d080e3 to b17ef8a96fb6afe3003d38cdec83afabe3ec9111.

Changelog

Sourced from gojiplus/py-canon/.github/workflows/reusable-ci.yml's changelog.

Changelog

All notable changes to this project are documented here.

The format follows Keep a Changelog. Release tags match the version committed in pyproject.toml; the fleet-facing v1 tag is a moving pointer advanced by the promote workflow after green CI, not a release of its own.

[Unreleased]

Added

• Reusable CI callers can set test-timeout-minutes and wheel-timeout-minutes when a complete test suite legitimately exceeds the default 30- and 20-minute job budgets. The defaults remain unchanged.

[1.3.0] - 2026-08-26

Fixed

• The pydoclint step reads [tool.uv.build-backend] module-name before guessing the package directory from the distribution name. finite-sample/optimal-classification-cutoffs ships optimal_cutoffs/, so the guess looked for optimal_classification_cutoffs/, found nothing, and hard-errored — the adoption had to pass run-pydoclint: false on a package that is clean under pydoclint 0.9.1, so a conforming repo silently lost the check. module-root is honoured too.

Fixed

• pre-commit runs the project's own ruff instead of a separately pinned rev. The dev group's ruff floats and CI resolves it from uv.lock, so an exact rev: was a second version drifting against it — and not harmlessly: ruff 0.16 formats Python inside Markdown and 0.15 does not, so pre-commit run --all-files passed while ruff format --check failed in CI on the same README, across five repos. The hooks are local now, running uv run ruff, so there is one version to reason about. The format hook also covers Markdown, which is where the two disagreed.

• The auto-merge sweep dispatches CI on the branch it merged into. A push made with GITHUB_TOKEN does not trigger workflows, so an auto-merged Dependabot PR left the default branch at a commit no CI run ever covered — on gojiplus/rowvoi, HEAD had zero runs for its SHA while the passing run belonged to a since-deleted PR branch. fleet_triage reads default-branch runs, so it reported on an older commit than HEAD and could clear or flag the wrong thing. The CI shim gains a workflow_dispatch trigger to receive it; a repo that has not picked that up yet gets a warning rather than a failed sweep.

... (truncated)

Commits

• b17ef8a Meet the Python floor this repo publishes
• d589aca Bump ruff from 0.16.3 to 0.16.4 in the python-minor-and-patch group (#74)
• d07e55c Allow callers to extend CI timeouts (#73)
• d30ecea Release py-canon 1.3.0 (#72)
• f8be1a8 Quote what the step printed, not what it was about to run (#71)
• bcd041e Run CI on the branch the auto-merge sweep just merged into (#70)
• 934433f Run the project's own ruff in pre-commit (#69)
• 9eee83f pydoclint: read module-name before guessing from the distribution name (#68)
• 507af49 Let yield types follow the same rule as return types (#67)
• 6d046c6 Cite a version, not just a name (#65)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #5.