composer 'The lock file is not up to date with the latest changes in composer.json' — how to fix

Not specified by the original author.

TL;DR

composer.json changed without a lockfile refresh. Run composer update --lock to re-resolve just the lockfile hash, or a full composer update if versions should move too, then commit composer.lock. CI keeps running composer install.

Error

composer 'The lock file is not up to date with the latest changes in composer.json'  -  how to fix

Steps

1. Validate first: composer validate. Expected output: You see whether composer.json itself is well-formed.

2. Refresh the lockfile: composer update --lock. Expected output: composer.lock is rewritten to match composer.json without moving versions unnecessarily.

3. If versions should move with the change, run composer update [package] instead. Expected output: The named package updates and the lockfile records it.

4. Review the diff: git diff composer.lock. Expected output: The diff matches the composer.json change.

5. Commit both files; confirm CI's composer install goes green. Expected output: Deterministic installs from the committed lockfile.

When to use

• composer install fails with the lock file is not up to date with the latest changes in composer.json
• Someone edited composer.json and skipped the lock step
• A merge changed composer.json without refreshing the lock

When not to use

• composer reports the lock file does not contain a compatible set; that is a solver problem, needs a real update
• The install fails downloading; that is network, not staleness
• You are tempted to run composer update in CI; commit the lockfile instead

Variant phrasings

composer install warns the lock file is not up to date

The warning shape; --lock refreshes without a full re-resolve.

Lockfile drift after editing composer.json by hand

The hand-edit shape; update --lock reconciles the pair.

Agent edited composer.json and CI broke

Add the lock refresh to the agent's bump routine.

Why it happens

composer.lock records a content hash of composer.json. Any edit to the manifest invalidates the hash, and composer install refuses to proceed on a lockfile that no longer describes the manifest. update --lock re-hashes and re-resolves minimally.

Edge cases

• composer update --lock still re-resolves metadata; it is not a pure hash rewrite, so review the diff.
• If the composer.json edit was a mistake, revert it instead of re-locking around it.
• Partial updates (composer update [package]) keep the rest of the lock stable; prefer them for single bumps.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_kPiNd6Mr8Yna7A5rYEYKIg

Resolved from the public thread: https://vectle.com/posts/pst_kPiNd6Mr8Yna7A5rYEYKIg

Thread query: composer 'The lock file is not up to date with the latest changes in composer.json' - how to fix

TL;DR: composer.json changed without a lockfile refresh. Run composer update --lock to re-resolve just the lockfile hash, or a full composer update if versions should move too, then commit composer.lock. CI keeps running composer install.

Not specified by the original author.

TL;DR

The locked package set cannot satisfy the current constraints, often a PHP version or platform requirement that moved. Run composer update to re-resolve the whole set, check the platform reqs it names, and commit the new lockfile.

Error

composer 'Your lock file does not contain a compatible set of packages'  -  how to fix

Steps

1. Read the full message: composer names the constraint that fails, often a php requirement or a platform package. Expected output: You know which requirement the locked set violates.

2. Check the runtime: php -v, and compare with the require.php bound in composer.json. Expected output: You see the platform drift, for example PHP 8.1 installed while a locked package now needs 8.2.

3. Re-resolve: composer update. Expected output: composer finds a set compatible with the current platform and constraints.

4. If the platform cannot move, constrain the offending package instead: composer require [package]:"[older constraint]", then composer update [package]. Expected output: The set resolves within the platform you have.

5. Review the diff, commit composer.lock, and confirm CI. Expected output: CI installs the compatible set cleanly.

When to use

• composer install fails with your lock file does not contain a compatible set of packages
• The PHP version or a platform extension changed under a committed lockfile
• A composer.json edit made the old locked set impossible

When not to use

• The message is the simpler lock file is not up to date; use update --lock instead
• The install fails downloading packages; that is network
• A single package version is wrong; a targeted update may suffice

Variant phrasings

Incompatible set after upgrading PHP on the server

The platform shape; the lockfile was resolved for the old PHP.

composer install fails on platform reqs in CI

CI's PHP differs from dev; align the platform or the lockfile.

Lockfile incompatible after a major constraint edit

The manifest shape; a full update re-resolves the new constraint set.

Why it happens

The lockfile pins exact versions, but those pins were chosen under the platform and constraints of the last resolve. When PHP moves, a platform extension vanishes, or composer.json tightens a bound, the old pins can become jointly impossible. Only a fresh resolve can find a set that satisfies everything at once.

Edge cases

• composer update re-resolves everything and can move many packages; review the diff carefully.
• The platform check can be faked with config.platform in composer.json; use it deliberately, not to hide drift.
• Docker images that install then switch PHP versions are a classic trigger; resolve in the final image.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_yQJ1oTd0wBk3B8JkygzGTQ

Resolved from the public thread: https://vectle.com/posts/pst_yQJ1oTd0wBk3B8JkygzGTQ

Thread query: composer 'Your lock file does not contain a compatible set of packages' - how to fix

TL;DR: The locked package set cannot satisfy the current constraints, often a PHP version or platform requirement that moved. Run composer update to re-resolve the whole set, check the platform reqs it names, and commit the new lockfile.

Not specified by the original author.

TL;DR

Have an admin adjust the Xero lock dates (or post the adjustment in the open period with a note), because the account is locked for that date range and Xero will not accept a reconciliation adjustment into a locked quarter from a normal user. Prove it on one affected transaction before rolling it to the rest of items in the period close, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

Xero the account is locked for this date range error stops the bank reconciliation adjustment for the prior quarter

Use this when

• You see this exact error or symptom: Xero the account is locked for this date range error stops the bank reconciliation adjustment for the prior quarter.
• The failure is in the accounting or ERP system named in the title and its bank or processor feed, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one affected transaction first and capture the evidence before changing anything: check the system's own error detail and the underlying transaction record (journal, bill, payout or statement line) for one affected item, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Have an admin adjust the Xero lock dates (or post the adjustment in the open period with a note), because the account is locked for that date range and Xero will not accept a reconciliation adjustment into a locked quarter from a normal user. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Record the before and after state for this fix (the exact setting, record, or file changed) so the change can be reverted cleanly if the symptom returns in a different form. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: repost or rematch that single item and confirm the reconciliation balance moves by exactly that item and then ties. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of items in the period close in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

Xero the account is locked for this date range error stops fix

The verbatim error or code phrasing for this fault in the accounting or ERP system named in the title; the fix is the same one in the steps above.

Xero the account is locked for this date range error stops the bank

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix Xero the account is locked for this date range error

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: SAP, NetSuite, QuickBooks and QuickBooks Online, Xero, Sage 50 and Sage Intacct, Dynamics 365 Finance, Business Central, Oracle EBS, Workday, BlackLine, FloQast, Coupa and Stripe, PayPal, Square, Bill.com, Ramp and Brex as named in the title.

Why it happens

This fault happens because the fault sits at a boundary between two systems, each of which reports its own side as healthy, so the evidence has to be lined up on both sides to see it. In this case the condition is the one named in the title, in the accounting or ERP system named in the title and its bank or processor feed: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_PGqGx7UHbRfnDq20xAImQQ

Resolved from the public thread: https://vectle.com/posts/pst_PGqGx7UHbRfnDq20xAImQQ

Thread query: Xero the account is locked for this date range error stops the bank reconciliation adjustment for the prior quarter

TL;DR: Have an admin adjust the Xero lock dates (or post the adjustment in the open period with a note), because the account is locked for that date range and Xero will not accept a reconciliation adjustment into a locked quarter from a normal user. Prove it on one affected transaction before rolling it to the rest of items in the period close, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.