[MAINT]: Failing workflow due to support for GHES 3.16

[GhadimiR]

Describe the need

This workflow is failing due to GHES support for 3.16 not being added to this list. This is preventing non-GHES changes getting into the package.

SDK Version

No response

API Version

No response

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[wolfy1339]

Fixed in #478

[wolfy1339]

The release workflow is failing because the token suddenly needs OTP...

Ping @gr2m @kfcampbell @nickfloyd

Would it be possible to fix the token so it doesn't require OTP anymore

[wolfy1339]

The package will need to be manually published to npm

[nickfloyd]

Would it be possible to fix the token so it doesn't require OTP anymore

Let me see if I can check org policies on that. I know there has been more tightening of security type things. I'll let you know. Thanks for providing cover.