Open kltm opened 1 month ago
@geneontology/developers , is anybody besides me using for-pay features for GO?
Talking to @pkalita-lbl and @sierra-moxon , it seems that the warning message may be in error? Now https://support.github.com/ticket/personal/0/2821198
In a recent email from GitHub titled "Important Announcement Re: Pages Legacy Worker Sunset", it is explained that:
"Since August 2022, GitHub Pages sites have been built and deployed with GitHub Actions. However for repositories where Actions is unavailable, we used the legacy pagesworkers for Pages builds and deployments."
They will be shutting this "pageworkers" bit down on June 30th.
Looking through various repositories that use GitHub Pages, only the GO seems to be affected with the warning so far (https://github.com/geneontology/geneontology.github.io/settings/pages). That fine, but the wonky part is a little after:
"For those on legacy paid plans (Gold, Silver, etc.) where Actions is unavailable, we suggest the following..."
We do seem to be on the legacy Bronze plan, which apparently does not have Actions for page deployment?
(Honestly, more than anything else, this looks like an attempt to move people onto per-seat licensing under the guise of security.)
I'm not quite sure yet the easiest way forward here. To start though:
At my end, the two sensitive repos would be
go-interal
andoperations
, but I could take those elsewhere are make GO a "free" Org, with nothing private and (I believe) bypass the restrictions. Any other thoughts on this? @cmungall?