Skip to content

(Wrong) fix for bundle lock edge case#7376

Closed
deivid-rodriguez wants to merge 1 commit intomasterfrom
fix-lock-update-patch-edge-case
Closed

(Wrong) fix for bundle lock edge case#7376
deivid-rodriguez wants to merge 1 commit intomasterfrom
fix-lock-update-patch-edge-case

Conversation

@deivid-rodriguez
Copy link
Contributor

What was the end-user or developer problem that led to this PR?

The problem is #7369. However, after further thought I don't think this is a good solution and we should only aim to provide a better error message here.

What is your fix for the problem, implemented in this PR?

Bring lockfile up to date when bundle lock --update foo --patch --strict is given with an out of date lockfile.

I don't think we want to do that, really.

Make sure the following tasks are checked

Bring lockfile up to date when `bundle lock --update foo --patch
--strict` is given with an out of date lockfile.
@deivid-rodriguez
Copy link
Contributor Author

I'm replacing this wrong approach with #7527.

@deivid-rodriguez deivid-rodriguez deleted the fix-lock-update-patch-edge-case branch March 21, 2024 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant