Additions to the GitHub Action are not necessary.

@afragen ok, my understanding from the docs for the Release Asset header (https://git-updater.com/knowledge-base/required-headers/) made it seem like if there were more than 1 release asset per release it needed this naming convention, and since we upload multiple assets I thought this was necessary?

coverage: 84.574%. remained the same
when pulling 710d7be on jasonbahl:fix/3418-github-updater
into b3ce4f0 on wp-graphql:develop.

I'll check this more closely and let you know where the current release asset points to.

I have to thank you @jasonbahl as I haven't really encountered anyone who has more than one release asset per release. I was previously picking up the first release asset, which in your case would be schema.graphql.

I've created a fix in my develop branch that will pick the release asset whose name starts with the repo's slug. Therefore it is not necessary to include the version number.

I should merge this and release by early next week. I will also update my KB doc. Thanks.