cpovirk 621416a240 Modernize cancellation configuration. ...

https://github.com/google/guice/commit/35173790910fd604e01c763df2ce9c4ae33e5198 probably used the best tools available in 2022. But this PR's approach, which we've been using with success [in Guava](https://github.com/google/guava/blob/0adf237b742d899d00239dfeefdd42807ff46a83/.github/workflows/ci.yml#L14-L17) and in other projects, looks to be [the recommended approach](https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#example-using-a-fallback-value) nowadays.

In particular, I wonder if the current setup is over-canceling: Currently, I see reports like ["Canceling since a higher priority waiting request for ci-main-b7c7483a46afadd43a2f04935aaee5ff0cd09145 exists"](https://github.com/google/guice/actions/runs/30832661591/job/91750157428) on a large number of jobs, causing GitHub to report the overall CI status as "failure."

RELNOTES=n/a
PiperOrigin-RevId: 958535716

2026-08-03 13:07:48 -07:00

..

actions

Annotate toProvider(..) methods to specify that providers can return null.

2025-03-07 19:00:18 -08:00

workflows

Modernize cancellation configuration.

2026-08-03 13:07:48 -07:00