Update Lockfile

[github-actions]

This pull request relocks the dependencies with conda-lock. It is triggered by update-lockfile.

[zaneselvans]

This was just a test of the workflow_dispatch behavior, which seems to work fine! Which is good because it's the same behavior as the schedule triggers.

[zaneselvans]

Hmm. Why isn't docker-build-test running as a check here? It's supposed to be triggered on pull_request which by default includes the creation event type but it didn't kick off here. Do you see anything obvious that would prevent it from being run here @jdangerx @bendnorman ?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (a886635) 88.6% compared to head (aa13a5f) 88.7%.
Report is 60 commits behind head on conda-lockfile.

Additional details and impacted files

@@              Coverage Diff               @@
##           conda-lockfile   #3022   +/-   ##
==============================================
  Coverage            88.6%   88.7%           
==============================================
  Files                  91      91           
  Lines               10991   11010   +19     
==============================================
+ Hits                 9749    9768   +19     
  Misses               1242    1242           

Files	Coverage Δ
src/pudl/analysis/allocate_gen_fuel.py	91.3% <ø> (ø)
src/pudl/etl/glue_assets.py	98.2% <ø> (ø)
src/pudl/extract/eia923.py	100.0% <100.0%> (ø)
src/pudl/extract/excel.py	96.3% <100.0%> (-0.5%)	⬇️
src/pudl/metadata/classes.py	86.5% <100.0%> (+<0.1%)	⬆️
src/pudl/metadata/constants.py	100.0% <ø> (ø)
src/pudl/metadata/fields.py	100.0% <ø> (ø)
src/pudl/metadata/resources/eia.py	100.0% <ø> (ø)
src/pudl/metadata/resources/eia923.py	100.0% <ø> (ø)
src/pudl/metadata/sources.py	100.0% <ø> (ø)
... and 8 more

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bendnorman]

Hmm seems strange the tox-pytest workflows ran on pull_request but the docker-build-test. Do you think it has something to do with github's policy about triggering workflows using GITHUB_TOKEN:
https://github.com/catalyst-cooperative/pudl/blob/ce1b983b8242e8ee6d684a788804518851392049/.github/workflows/update-lockfile.yml#L41C1-L48C48

[zaneselvans]

That policy is why I'm using a @pudlbot PAT rather than the generic GITHUB_TOKEN in the checkout. to get all the tests to retrigger. Maybe I need to use that in the step that makes the new PR?

[zaneselvans]

But yeah, why did it trigger some of the tests and not others?