Thanks for the PR @bomoko! I'll take a look when I have some free cycles.

Nice work @bomoko --great follow up to #609. I made a couple of tweaks, but otherwise looks great 💯 :

• Unexported the PHP types used for unmarshaling
• Removed the unused V1 composer install.json type
• Small rename of the PHP cataloger names

One last change is needed before we can merge this, @bomoko; we require that all commits are signed before merging into the baseline (see CONTRIBUTING.md) . Shout out if you have any questions about this!

Thanks so much @wagoodman - I think I understand how to sign the previous commits if I rebase and amend with -S, does this seem right?
Problem with this is that I believe I end up signing your commits (whether I rebase on the branch directly, or if I cherry-pick into another branch). I'm a little unsure about how best to deal with that (or whether it's even a problem).

Is it a problem that I end up signing your commits? Or do the commits simply need to be signed?
Alternatively, I could make a new commit out of yours and sign that.
Any advice you could give here would be great.

@bomoko indeed rebasing with -S will do the trick 👍 (it's OK if you end up signing my commits)

Awesome, thanks @wagoodman - since signing the commit changes the hashes, I think I'm going to need to push force the branch to get the history right. Any objections? (I can also open a new PR)

Edit: Let me just do it - if it's a faux pas I'll open up a new PR ;)

@bomoko force push away! Our take on this is that commits on development branches are up to the author, so you can rearrange as you like. We tend to squash merge PRs into main in the end.