feat: implement --force flag for lock

[11happy]

Summary

This PR fixes #15220

Test Plan

I have tested the updated force flag working.

CC

@zanieb

[zanieb]

I think we still probably want to use the existing versions instead of ignoring the existing lockfile entirely? This might be kind of hard to teach though 🤔

I think this doesn't accomplish the goal from the issue.

[11happy]

Hii @zanieb
I see your point about my current implementation not addressing the core issue. To solve the issue , I am thinking to approach it like this -
For the --force flag approach:
I can set the ValidatedLock to Preferable/Versions to use existing versions but force a rewrite when --force flag is used.

OR

When validation succeeds and we reach this section:

Some(ValidatedLock::Satisfies(lock)) => {
    // Print the success message after completing resolution.
    logger.on_complete(lock.len(), start, printer)?;
    Ok(LockResult::Unchanged(lock))
}

Should I add format checking here? If there's a format mismatch (missing revision = 3, missing upload-time fields, etc.),

How should I apprach format detection ?
I saw the implementation of Lock & it has this revision field,
does checking revision field would work ?
Also is there a suggested way to detect missing upload-time fields or other format indicators?

I'd appreciate any pointers to help me move forward. Also, could you point me to resources about uv lockfile format internals?

Thanks for your patience as I work through this : )

[zanieb]

I think you're on the right track with changing validation. I think we want to change

uv/crates/uv/src/commands/project/lock.rs

Line 942 in b1fbb52

async fn validate<Context: BuildContext>(

to just immediately return Ok(Self::Preferable(lock)) if force is set. I think that should be sufficient to force us to do a new resolution and write to the lockfile?

[11happy]

I think you're on the right track with changing validation. I think we want to change

uv/crates/uv/src/commands/project/lock.rs

Line 942 in b1fbb52

async fn validate<Context: BuildContext>(

to just immediately return Ok(Self::Preferable(lock)) if force is set. I think that should be sufficient to force us to do a new resolution and write to the lockfile?

Thank you, I will do it likewise : )

[zanieb]

I think you'll need to merge / rebase with the overlapping work in #15994

[11happy]

have rebased it, done @zanieb : )

wait let me fix CI errors & get back !

[11happy]

Hii @zanieb, I’ve fixed all the CI errors. Could you take a look when you get a chance?
Thank you : )

[11happy]

gentle ping !