I've got a TYPO3 project with a site extension in a subdirectory. This subdirectory is used as composer package, referenced as a path repository:

Root composer.json:

{
    "require": {
        "mogic/t3x-srh": "@dev",
   },
    "repositories": [
        {
            "type": "path",
            "url": "public/typo3conf/ext/srh",
            "options": {
                "symlink": false
            }
        }
    }
}

This works fine unless I want to update packages in the root composer.json file when I am in a feature branch. When running composer update --lock (because of e.g. a rebase conflict within composer.lock), I get:

• Root composer.json requires mogic/t3x-srh == dev-develop, found mogic/t3x-srh[dev-main] but it does not match your constraint and is therefore not installable.

I tried setting "reference": "none", in the path repository options, but that does not help.

Another problem: When running "composer update" in a branch, it updates the local packages:

Upgrading mogic/t3x-srh (dev-develop => dev-SRH-1479-typo3v12): Source already present

What can I do to make composer ignore the current branch I am on and do not give me any conflicts?

composer.lock contains references the branch I last updated the packages, which seems to be the problem:

        {
            "name": "mogic/t3x-srh",
            "version": "dev-develop",
            [...]
        }