-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Release integration for Sopel 8.0.0 #47
Conversation
The result of lengthy collaboration. Commit metadata does not *quite* reflect the actual authorship timeline... ;-) Co-authored-by: James <[email protected]> Co-authored-by: mal <[email protected]>
efa8dbc
to
d9fc164
Compare
Ooh, this is gonna be a fun puzzle. We are going to need updates from #38 to build successfully with the updated
I knew reorganizing pages would come back to bite us one day! 😁 Edit: Merging #38 and applying a bit of extra fixum on top yielded a successful build. It might still contain some broken links that don't use the |
Upstream, `sopel/modules/` became `sopel/builtins/`, so the script here to `document_sopel_plugins.py` had to be updated at the same time. NOTE: This is a WIP commit, not pointing to the final version of 8.0.0!
f9ba9e9
to
a74fa39
Compare
Sopel 8 upgrade guide
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good.
38f30e0
to
6cfd40e
Compare
6cfd40e
to
4912e3e
Compare
This PR will serve as a pre-release integration point for all the moving parts that come with the new Sopel 8.0.0 release:
I'm opening this in a non-working state at first. Updating the
_sopel/
submodule currently raises an unhelpful error in Netlify deploy logs as shown below, and I wanted to move debugging that out of #46 where I started it.Cryptic Netlify error
Generally, it also just seems like a good idea to have an intermediate stop where all of the 8.0.0 updates will come together before they hit the site's production domain. Fixing unexpected build errors is less stressful on a PR branch than on
master
. 😁Once
_sopel/
is sorted out, other PRs about 8.0.0 prep can be edited to use this branch as their base instead.