docs: Add release notes for Boost 1.86 #749
Conversation
|
The one job that failed here was "posix (clang, 14,17, macos-11)". That is a bit strange, because a documentation update should not cause CI failure. Here's what the summary says:
That should not happen - unless no such runners are available at all. Turns out they are no longer available: https://github.blog/changelog/2024-05-20-actions-upcoming-changes-to-github-hosted-macos-runners/
We are now past the date when the macOS 11 runner image was removed, and that is why that CI job failed. |
|
Thanks for looking into this and the doc improvements. I don't know much about the CI setup on this project but I think that @mloskot who also contributed to boostorg/boost-ci used it to set it up. So maybe it is just a question of merging with the latest boost-ci (the GH actions part)? |
There was a problem hiding this comment.
Thank you @striezel for this update, your efforts are priceless!
@sdebionne Yes, I did some contributions to boost-ci project, but AFAIR I stopped using it for GIL a while ago, some time around dropping use of Travis CI. Then, I have been following Boost.MP11's https://github.com/boostorg/mp11/blob/develop/.github/workflows/ci.yml to catch up with changes and deprecations in GitHub Actions.
Long story short, I think we can ignore this change and approve this PR.
@striezel You are right, I think we should not run the whole CI for changes like this. It looks like we could improve it with exclusions based on paths/files filter, https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-excluding-paths
Description
Includes release notes for the changes seen in the table in #748, i.e. the changes for a potential Boost 1.86 release of GIL.
References
See #748.
Tasklist