force repro updates hashsums of frozen stages' dependencies

[TimOliverMaier]

Hi!

Today I realized that running dvc repro -f updates the dependencies of frozen stages in dvc.lock. dvc repro without force does not. Is that intended? If so, why? Personally, I would prefer to be able to force repro all unfrozen stages without updating anything in the frozen stages. I think it also breaks the idea that dvc.lock tracks which inputs led to which outputs.

A minimal example to reproduce the issue:

dvc.yaml:

stages:
  first_stage:
    cmd: python foo.py
    deps:
    - foo.py
  second_stage:
    cmd: python bar.py
    deps:
    - bar.py
    - foo.py

foo.py:

print("foo")

bar.py:

print("bar")

1. dvc repro
2. dvc freeze second_stage
3. change foo.py and run dvc repro -> deps of second_stage do not change in dvc.lock
4. run dvc repro -f -> deps of second_stage change

Can someone explain why this would be intended behaviour? Otherwise I am happy to open an issue.

Best
Tim