-
Notifications
You must be signed in to change notification settings - Fork 302
Switch to upstream Zola #1632
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
Switch to upstream Zola #1632
Conversation
d5f9349
to
940afa8
Compare
I tried and failed to run the snapshot tests in CI. The reason is that only one version of zola is installed for both the "before" and "after" builds of the site. However, the new version of zola we're using relies on the However, I did run the tests locally:
The tests passed, so I'm confident there is no impact on the site. |
Maybe worth mentioning: If this is merged, people who currently have my fork of zola installed will run into build errors (due to the unknown "permalink" value). The solution is to install the new version. I don't expect this to happen when Zola has an official release and we can switch to using those binaries, they should be compatible. |
940afa8
to
58cb2ad
Compare
58cb2ad
to
1cf1145
Compare
1cf1145
to
39d9396
Compare
|
bb9fc68
to
966d1b3
Compare
All of the patches we needed for the migration have been merged upstream (with some modifications, hence the `sort_by = "permalink"` diff). We use a submodule of Zola so we can better control the version of Zola that blog authors are running locally.
966d1b3
to
e3bc8a9
Compare
All of the patches we needed for the migration have been merged upstream (with some modifications, hence the
sort_by = "permalink"
diff).We don't know how long it will take for Zola to cut a new release, so let's provide our own binaries to blog authors in the meantime.
Rendered