search

standards-hub / docs

A documentation template made with Nuxt UI Pro.
https://standards-hub.github.io/docs/
0 stars 0 forks source link

GitHub announcement - how is this affecting us #77

Open jpradocueva opened 2 months ago

jpradocueva commented 2 months ago

https://github.blog/changelog/2022-07-27-github-pages-custom-github-actions-workflows-beta/

See the announcement that we received today from GitHub regarding GitHub Pages. How is this affecting what we have? GitHub Hello,

We are writing to inform you about an important update regarding GitHub Pages.

What is happening?

Delivering on our continued commitment to enhance security, protect your data, and deliver an overall improved experience, we will be phasing out our legacy pagesworker architecture by the end of June 2024.

What is replacing legacy pagesworker?

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.

Going forward, GitHub Actions will become a requirement for deploying Pages sites that require a build step, such as those utilizing Jekyll. We chose to implement this change because Actions provides developers a modern, secure sandbox that surpasses the capabilities of pagesworker. With Actions you get your choice of operating system, log streaming, dependency caching, custom gates, and modern CI/CD features. Additionally, we are pleased to announce the general availability of the feature allowing you to delegate Pages deployments to Actions alongside a source branch.

How can I tell if my Pages site will be impacted?

If your Pages site is being built by the legacy infrastructure, a warning message will be displayed in your Pages settings starting today. Note that the vast majority of pages sites have already been leveraging Actions. We only fall back to the legacy build infrastructure if Actions is unavailable in your repository.

We understand that change can be challenging, and we apologize for any inconvenience this may cause. Our priority is to continue delivering a more secure platform for all of our users, and we appreciate your understanding as we make these necessary adjustments.

If you have any questions or concerns about this announcement, please don't hesitate to reach out to our support team for assistance. We are here to help and ensure a smooth transition for all our users.

Thank you for being a valued member of the GitHub community.

GitHub

FroudeDescartes commented 2 months ago

@jpradocueva I have a rough idea about the topic that they are discussing, but since I haven't had any experience with site deployment using GitHub, I will need to take a closer look and probably consult Dejan about it as well. At our meeting on Friday I will have definite answer.

jpradocueva commented 2 months ago

@FroudeDescartes Thanks, Filip; we will discuss it on Friday.