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
Make compressed sitemap deterministic #2100
Conversation
Since #1010 (4 years ago) we support the That said, I'm curious if perhaps the gzip lib already makes use of the env variable. After all, our users who use the variable have not complained about the sitemap. Finally, I see that the docs for the |
Interesting. Where does that date get rendered? Removing the archive makes our builds reproducible without setting that environment variable. |
In the builtin themes, the
mkdocs/mkdocs/themes/mkdocs/base.html Lines 197 to 204 in a4eb4eb
mkdocs/mkdocs/themes/readthedocs/base.html Lines 156 to 163 in a4eb4eb
In both cases, the comment is the past thing after the closing <!--
MkDocs version : 1.1
Build Date UTC : 2020-02-26 23:50:49
--> That is the actual date and time the site was built and pushed live, which roughly corresponds with the time of the last release. |
Ah I see, we minify the html so we have no comments. |
@waylan Addressed! FYI a new version of flake8 was released, hence the errors. |
Sigh. Thanks for the heads-up. We can ignore that here as it is unrelated to this change.
Also, we need a note added to the release notes (under version 1.1.1). Otherwise, this looks great. Thanks for the work on this. |
Done, thank you! Any idea when 1.1.1 will be released? |
I expect very soon. |
FYI, version 1.1.1 has been released. |
Thank you!!! |
Our deployment step for https://datadoghq.dev/integrations-core/ should only trigger when a change occurs in the built site. However, every build was different because gzip includes the timestamp in its header.
cc @waylan since you were involved with #1130