-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Versions out of sync #810
Comments
Note: not having 222 and 223 on GitHub releases also means it's hard to see what's changed. |
@yoannchaudet Hey! Is there a way to run a Page Build job on the pages.github.com site periodically? Maybe a GitHub Action could fire off the build? Many folks use https://pages.github.com/versions/ (and |
Hello here! Thank you for pointing these inconsistencies, this was not intended. Versions 222 and 223 did not include any changes relevant to the build process itself and just helped support https://github.blog/changelog/2021-12-16-github-pages-using-github-actions-for-builds-and-deployments-for-public-repositories/. We should not be out of sync in so many locations! I'll make sure we update our procedure to release @parkr (hi!) yes! We can definitely automate the rebuilds for pages.github.com ❤️ |
@yoannchaudet Hi! Thank you so much! ❤️ |
Thanks @parkr for pointing to the right person! And also for still being active around here after your departure to greener pastures. 🙇♂️💪 Thanks for committing to cleaning up the confusion @yoannchaudet! |
Forgot to close that with the last update. We should be in-sync everywhere or within a few hours during any upgrade. |
Confirmed. Release 227 just went out 5 hours ago and it's everywhere except https://pages.github.com/versions/ which is on 226. Deployment might take a while as you said. |
pages.github.com is updated every 6 hours so it's a matter of minutes now :) |
Before submitting an issue, please be sure to
bundle update github-pages
)This issue affects
What did you do (e.g., steps to reproduce)
Want to update my
Gemfile
to match GitHub's version.What did you expect to happen?
Find the specific version GitHub uses at the moment.
What happened instead?
Confusion:
At this point I can't tell if the
/versions/
page is outdated (August?!) or GitHub is not using the latest from its own project?!Please clarify and update scripts/documentation to keep these 4 numbers in sync.
The text was updated successfully, but these errors were encountered: