Did we also intentionally skip v2.2 in favor of v2.3?

@justlevine I think the skip must be something going on in my release tooling. It should not have skipped but something in my workflow triggered it to that I need to debug. 😬

Ironically, the automations I put in place to prevent this type of mistake were responsible for this type of mistake 🤦🏻‍♂️

@justlevine it looks like maybe I had a 2.2.0 release that didn't properly run and I wasn't paying enough attention to the details because the workflows report they succeeded, but really they didn't. (see: https://github.com/wp-graphql/wp-graphql/actions/runs/13957891456/job/39073292846#step:9:864)

🤔

• https://github.com/wp-graphql/wp-graphql/actions/runs/14184340363
• https://github.com/wp-graphql/wp-graphql/actions/runs/13957891456

Got some fixing to do in my automations. 🤦🏻 😬

2.2.0 and 2.3.0 both are not properly deployed to WordPress.org, it seems 🤔

@justlevine looks like I had an error in the workflow that was passing the v prefix of our release versions v2.2.0 and v2.3.0 which were causing some funky issues.

I have it strip the v before deploying to WordPress.org now.

Both 2.2.0 and 2.3.0 are on WordPress.org now and I manually published the 2.2.0 release to Github as well.

Hopefully this settles the kinks with the workflows. We might find some other issues as we go.

Thanks for pointing this out. Gave me a good chance to step back and look at things I was overlooking.

Code Climate has analyzed commit 071da61 and detected 0 issues on this pull request.

View more on Code Climate.

coverage: 84.17%. remained the same
when pulling 071da61 on fix/missed-since-tags
into 89238fc on develop.