-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: squidfunk/mkdocs-material
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 9.5.15
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: squidfunk/mkdocs-material
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 9.5.17
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 20 commits
- 69 files changed
- 9 contributors
Commits on Mar 23, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 5458039 - Browse repository at this point
Copy the full SHA 5458039View commit details
Commits on Mar 27, 2024
-
Configuration menu - View commit details
-
Copy full SHA for f27b93e - Browse repository at this point
Copy the full SHA f27b93eView commit details
Commits on Mar 31, 2024
-
Configuration menu - View commit details
-
Copy full SHA for ad72336 - Browse repository at this point
Copy the full SHA ad72336View commit details -
Co-authored-by: natakazakova <17986517+natakazakova@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 01b2dd1 - Browse repository at this point
Copy the full SHA 01b2dd1View commit details -
Switched to Babel's
format_datetimeto allow for time in formatted ……dates (#6981) * Use Babel's `format_datetime`, not `format_date` I am using MkDocs-Material 9.5.15 and Babel 2.14.0. When setting the config value `blog.post_date_format: "yyyy-MM-dd hh:mm:ss"`, the blog plugin crashes during compilation with the error "date objects have no hour field". I believe this is occurring because the plugin provides a `datetime` to `babel.dates.format_date`, which upcasts it to a plain, timeless, `date`. Making this change to use `babel.dates.format_datetime` instead resolved the error and demonstrated expected behavior. While I recognize that it is likely uncommon for a blog to want to include sub-date timestamps in any of these fields, I believe that the current documentation, > The format string must adhere to babel's pattern syntax and should not contain whitespace implies that _any_ of Babel's pattern markers are acceptable here. I would consider > The format string must adhere to Babel's pattern syntax for calendar dates and should not contain whitespace to also be a sufficient fix for this case. ---- Thank you for your effort in creating this project; it has been a wonderful benefit to my team, and this is the first minor problem we've had in months of using it. * Make the change in src/, not material/
Configuration menu - View commit details
-
Copy full SHA for abfac1a - Browse repository at this point
Copy the full SHA abfac1aView commit details -
Improved error handling on social plugin (#6818)
* fix(social): CairoSVG OSError handling in social plugin Related issue: #6817 Co-authored-by: Guts <1596222+Guts@users.noreply.github.com> * feat(docs): Add troubleshooting guide for CairoSVG crash --------- Co-authored-by: Kamil Krzyśków <kamilzary@gmail.com> Co-authored-by: Guts <1596222+Guts@users.noreply.github.com> Co-authored-by: Martin Donath <martin.donath@squidfunk.com>
Configuration menu - View commit details
-
Copy full SHA for a2cb35d - Browse repository at this point
Copy the full SHA a2cb35dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9e40207 - Browse repository at this point
Copy the full SHA 9e40207View commit details -
Configuration menu - View commit details
-
Copy full SHA for f2bfab9 - Browse repository at this point
Copy the full SHA f2bfab9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6c9ba87 - Browse repository at this point
Copy the full SHA 6c9ba87View commit details -
Configuration menu - View commit details
-
Copy full SHA for 29cf44b - Browse repository at this point
Copy the full SHA 29cf44bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0db4e66 - Browse repository at this point
Copy the full SHA 0db4e66View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8956524 - Browse repository at this point
Copy the full SHA 8956524View commit details -
Configuration menu - View commit details
-
Copy full SHA for e71f00b - Browse repository at this point
Copy the full SHA e71f00bView commit details -
Unicode, case-sensitive reference setting causes error below. ``` yaml.constructor.ConstructorError: expected a mapping node, but found scalar ``` Update related sections in the documentation to address this issue. Newer Python-Markdown has `slugify_unicode` built-in, so this ```yaml markdown_extensions: - toc: slugify: !!python/name:markdown.extensions.toc.slugify_unicode ``` also works for case-insensitive use cases. Fixes: ee1e675 ("Update slug reference")Configuration menu - View commit details
-
Copy full SHA for 7d6d8d7 - Browse repository at this point
Copy the full SHA 7d6d8d7View commit details
Commits on Apr 1, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 7e13ae6 - Browse repository at this point
Copy the full SHA 7e13ae6View commit details -
Configuration menu - View commit details
-
Copy full SHA for e741f80 - Browse repository at this point
Copy the full SHA e741f80View commit details
Commits on Apr 2, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 1041766 - Browse repository at this point
Copy the full SHA 1041766View commit details -
Co-authored-by: stcksmsh <107367925+stcksmsh@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for a3655e8 - Browse repository at this point
Copy the full SHA a3655e8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 78e93ac - Browse repository at this point
Copy the full SHA 78e93acView commit details -
Configuration menu - View commit details
-
Copy full SHA for 570161a - Browse repository at this point
Copy the full SHA 570161aView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 9.5.15...9.5.17