We're struggling to update our plugins because no matter what we do it seems we get authentication issues with checkout@v6 when using create-pull-request@v7.0.11 or create-pull-request@v8 despite these seemingly having the required changes for the auth changes in checkout@v6.
I'd appreciate suggestions as to what might be wrong, but given it works in some configurations, it looks like a lingering issue with compatiblity with checkout@v6.
The only combinations we can get working so far are:
checkout@v4 and create-pull-request@v6 (obviously using the old auth mechanism of checkout@v4)checkout@v6 and create-pull-request@v6 but only if we set persist-credentials: false on the checkout
(it's possible checkout 6 and create-pull-request 7.x might work with persist-credentials off, haven't gone there - but crucially it does not work with create-pull-request 8, see below)
So basically we can't get the latest checkout@v6 and create-pull-request working with the new auth scheme at all.
These combos give the same error —
checkout@v6 + create-pull-request@v8checkout@v6 + create-pull-request@v8 even if we set persist-credentials: false on the checkoutcheckout@v6 + create-pull-request@v7.0.11checkout@v4 + create-pull-request@v8checkout@v4 + create-pull-request@v7.0.11
Checking the base repository state
/opt/homebrew/bin/git symbolic-ref HEAD --short
ios/marc/actions-test-6.29
Working base is branch 'ios/marc/actions-test-6.29'
/opt/homebrew/bin/git remote prune origin
fatal: could not read Username for 'https://github.com/': Device not configured
Error: The process '/opt/homebrew/bin/git' failed with exit code 128
This combination also fails, but differently:
checkout@v6 + create-pull-request@v6
gives:
remote: Duplicate header: "Authorization"
fatal: unable to access 'https://github.com/tophatch/concepts/': The requested URL returned error: 400
Error: The process '/opt/homebrew/bin/git' failed with exit code 128
We're struggling to update our plugins because no matter what we do it seems we get authentication issues with
checkout@v6when usingcreate-pull-request@v7.0.11orcreate-pull-request@v8despite these seemingly having the required changes for the auth changes incheckout@v6.I'd appreciate suggestions as to what might be wrong, but given it works in some configurations, it looks like a lingering issue with compatiblity with
checkout@v6.The only combinations we can get working so far are:
checkout@v4andcreate-pull-request@v6(obviously using the old auth mechanism of checkout@v4)checkout@v6andcreate-pull-request@v6but only if we setpersist-credentials: falseon the checkout(it's possible checkout 6 and create-pull-request 7.x might work with persist-credentials off, haven't gone there - but crucially it does not work with create-pull-request 8, see below)
So basically we can't get the latest
checkout@v6andcreate-pull-requestworking with the new auth scheme at all.These combos give the same error —
checkout@v6+create-pull-request@v8checkout@v6+create-pull-request@v8even if we setpersist-credentials: falseon the checkoutcheckout@v6+create-pull-request@v7.0.11checkout@v4+create-pull-request@v8checkout@v4+create-pull-request@v7.0.11This combination also fails, but differently:
checkout@v6+create-pull-request@v6gives: