mkdocs-document-dates 3.1.2__tar.gz → 3.1.5__tar.gz

{mkdocs_document_dates-3.1.2 → mkdocs_document_dates-3.1.5}/PKG-INFO

@@ -1,9 +1,10 @@
 Metadata-Version: 2.4
 Name: mkdocs-document-dates
-Version: 3.1.2
+Version: 3.1.5
 Summary: An easy-to-use, lightweight MkDocs plugin for displaying the exact creation time, last modification time and author info of markdown documents.
 Home-page: https://github.com/jaywhj/mkdocs-document-dates
 Author: Aaron Wang
+Author-email: aaronwqt@gmail.com
 License: MIT
 Classifier: Programming Language :: Python :: 3
 Classifier: License :: OSI Approved :: MIT License
@@ -11,8 +12,9 @@ Classifier: Operating System :: OS Independent
 Requires-Python: >=3.7
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: mkdocs>=1.0.0
+Requires-Dist: mkdocs>=1.1.0
 Dynamic: author
+Dynamic: author-email
 Dynamic: classifier
 Dynamic: description
 Dynamic: description-content-type
@@ -33,8 +35,8 @@ An easy-to-use, lightweight MkDocs plugin for displaying the <mark>exact</mark>
 
 ## Features
 
-- Work in any environment, for Git-less environments, CI/CD environments (e.g. GitHub Actions), one-person collaboration, multi-person collaboration, etc
-- Support for manually specifying time and author info in `Front Matter`
+- Always display exact meta-info of the document for any environment (no-Git, Git, all CI/CD build systems, etc)
+- Support for manually specifying time and author in `Front Matter`
 - Support for multiple time formats (date, datetime, timeago)
 - Support for document exclusion mode
 - Flexible display position (top or bottom)
@@ -72,15 +74,14 @@ plugins:
   - document-dates:
       position: top            # Display position: top (after title)  bottom (end of document), default: bottom
       type: date               # Date type: date  datetime  timeago, default: date
-      locale: en               # Localization: zh zh_TW en es fr de ar ja ko ru, default: en
-      date_format: '%Y-%m-%d'  # Date format, Supports all Python datetime format strings, e.g., %Y-%m-%d, %b %d, %Y, etc
-      time_format: '%H:%M:%S'  # Time format (valid only if type=datetime)
+      locale: en               # Localization: en zh zh_TW es fr de ar ja ko ru, default: en
+      date_format: '%Y-%m-%d'  # Date format strings, e.g., %Y-%m-%d, %b %d, %Y, etc
+      time_format: '%H:%M:%S'  # Time format strings (valid only if type=datetime)
       exclude:                 # List of excluded files
         - temp.md              # Exclude specific file
         - private/*            # Exclude all files in private directory, including subdirectories
-        - drafts/*.md          # Exclude all markdown files in the current directory drafts, but not subdirectories
       
-      show_author: true        # Whether to display author: true false, default: true
+      show_author: true        # Show author or not, default: true
 
 ```
 
@@ -88,7 +89,7 @@ plugins:
 
 The plugin will automatically get the exact time of the document, will automatically cache the creation time, but of course, you can also specify it manually in `Front Matter`
 
-Priority: `Front Matter` > `Cache Files` > `File System Timestamps`
+Priority order: `Front Matter` > `Cache Files` > `File System Timestamps`
 
 ```yaml
 ---
@@ -106,7 +107,7 @@ modified: 2025-02-23
 
 The plugin will automatically get the author of the document, will parse the email and make a link, also you can specify it manually in `Front Matter`
 
-Priority: `Front Matter` > `Git Author Info` > `PC Username`
+Priority order: `Front Matter` > `Git Author` > `site_author (mkdocs.yml)` > `PC Username`
 
 ```yaml
 ---
@@ -122,27 +123,42 @@ email: e-name@gmail.com
 
 ## Customization
 
-The plugin supports deep customization, such as icon style, font style, theme color, animation type, dividing line, etc. All of it can be customized by modifying the code in the corresponding file (I've already written the code and comments, you just need to turn on the switch and change the value):
-
-- Style & Theme: `docs/assets/document_dates/user.config.css`
-- Properties & Animations: `docs/assets/document_dates/user.config.js`
-- Localized languages: `docs/assets/document_dates/languages/` , refer to the template file `en.json` for any additions or modifications
-- timeago.js localization: `timeago.min.js` only contains English and Chinese by default, if you need to load other languages, you can configure it as below (choose one):
-    - In user.config.js, refer to [the demo commented out](https://github.com/jaywhj/mkdocs-document-dates/blob/main/mkdocs_document_dates/static/config/user.config.js) at the bottom, translate it into your local language
-    - In mkdocs.yml, add the following two lines to configure the full version of `timeago.full.min.js` to load all languages at once
-    
-        ```yaml
-        extra_javascript:
-          - assets/document_dates/core/timeago.full.min.js
-          - assets/document_dates/core/timeago-load.js
-        ```
+The plugin supports deep customization, such as **icon style, font style, theme color, animation type, dividing line**, etc. All of it can be customized by modifying the preset values in the corresponding file (I've already written the code and comments, you just need to turn on the switch and change the value):
+
+|        Function：        | Location：                               |
+| :----------------------: | ---------------------------------------- |
+|     **Style & Theme**     | `docs/assets/document_dates/user.config.css` |
+| **Properties & Functions** | `docs/assets/document_dates/user.config.js` |
+| **Localized languages** | `docs/assets/document_dates/languages/` <br />refer to the template file `en.json` for any additions or modifications |
+
+**Tip**: when `type: timeago` is set, timeago.js is enabled to render time dynamically, `timeago.min.js` only contains English and Chinese by default, if you need to load other languages, you can configure it as below (choose one):
+
+- In `user.config.js`, refer to [the demo commented out](https://github.com/jaywhj/mkdocs-document-dates/blob/main/mkdocs_document_dates/static/config/user.config.js) at the bottom, translate it into your local language
+- In `mkdocs.yml`, add the following two lines to configure the full version of `timeago.full.min.js` to load all languages at once
+    ```yaml
+    extra_javascript:
+      - assets/document_dates/core/timeago.full.min.js
+      - assets/document_dates/core/timeago-load.js
+    ```
+
+**Demo Images**:
+
+![01-default-w](mkdocs_document_dates/demo_images/01-default-w.png)
+![02-change-icon](mkdocs_document_dates/demo_images/02-change-icon.png)
+![02-change-icon-color](mkdocs_document_dates/demo_images/02-change-icon-color.png)
+![04-default-pop-up](mkdocs_document_dates/demo_images/04-default-pop-up.png)
+![05-change-theme](mkdocs_document_dates/demo_images/05-change-theme.png)
+
+![06-change-theme](mkdocs_document_dates/demo_images/06-change-theme.png)
+![07-pop-up-from-top](mkdocs_document_dates/demo_images/07-pop-up-from-top.png)
+![08-pop-up-from-bottom](mkdocs_document_dates/demo_images/08-pop-up-from-bottom.png)
 
 ## Other Tips
 
-- In order to get the exact creation time, a separate cache file is used to store the creation time of the file, located in the doc folder (hidden by default), please don't delete it:
+- In order to always get the exact creation time, a separate cache file is used to store the creation time of the document, located in the docs folder (hidden by default), please don't delete it:
     - `docs/.dates_cache.jsonl`, cache file
-    - `docs/.gitattributes`, merge mechanism for cache file in case of multi-person collaboration
-- The Git Hooks mechanism is used to automatically trigger the storing of the cache (every time executes a git commit), and the cached file is automatically committed along with it. In addition, the installation of Git Hooks is automatically triggered when the plugin is installed, without any manual intervention!
+    - `docs/.gitattributes`, merge mechanism for cache file
+- The Git Hooks mechanism is used to automatically trigger the storing of the cache (on each git commit), and the cached file is automatically committed along with it, in addition, the installation of Git Hooks is automatically triggered when the plugin is installed, without any manual intervention!
 
 <br />
 
@@ -151,11 +167,11 @@ The plugin supports deep customization, such as icon style, font style, theme co
 A dispensable, insignificant little plug-in, friends who have time can take a look \^\_\^ 
 
 - **Origin**:
-    - Because [mkdocs-git-revision-date-localized-plugin](https://github.com/timvink/mkdocs-git-revision-date-localized-plugin), a great project. When I used it at the end of 2024, I found that I couldn't use it locally because my mkdocs documentation was not included in git management, then I don't understand why not read the file system time, but to use the git time, and raised an issue to the author, but didn't get a reply for about a week (the author had a reply later, nice guy, I guess he was busy at the time), and then I thought, there is nothing to do during the Chinese New Year, and now AI is so hot, why not with the help of the AI try it out for myself, it was born, born in February 2025
+    - Because [mkdocs-git-revision-date-localized-plugin](https://github.com/timvink/mkdocs-git-revision-date-localized-plugin), a great project. When I used it at the end of 2024, I found that I couldn't use it locally because my mkdocs documentation was not included in git management, I don't understand why not read the file system time, but to use the git time, and the filesystem time is more accurate, then raised an issue to the author, but didn't get a reply for about a week (the author had a reply later, nice guy, I guess he was busy at the time), and then I thought, there is nothing to do during the Chinese New Year, and now AI is so hot, why not with the help of the AI try it out for myself, it was born, born in February 2025
 - **Iteration**:
     - After development, I understood why not use filesystem time, because files will be rebuilt when they go through git checkout or clone, resulting in the loss of original timestamp information, and there are many solutions:
     - Method 1: Use the last git commit time as the last update time, and the first git commit time as the creation (there is a margin of error, but it's acceptable), mkdocs-git-revision-date-localized-plugin does this
-    - Method 2: You can cache the original time, and then read the cache subsequently. The cache can be in Front Matter of the source document or in a separate file, I chose the latter. Storing in Front Matter makes sense and is simple, but this will modify the source content of the document, although it doesn't have any impact on the body, but I still want to ensure the originality of the data!
+    - Method 2: You can cache the original time in advance, and then read the cache subsequently. The cache can be in Front Matter of the source document or in a separate file, I chose the latter. Storing in Front Matter makes sense and is easier, but this will modify the source content of the document, although it doesn't have any impact on the body, but I still want to ensure the originality of the data!
 - **Difficulty**:
     1. When to read and store original time? This is just a plugin for mkdocs, with very limited access and permissions, mkdocs provides only build and serve, so in case a user commits directly without executing build or serve (e.g., when using a CI/CD build system), then you won't be able to retrieve the time information of the file, not to mention caching it!
         - Let's take a straight shot: the Git Hooks mechanism was found, prompted by the AI, which can trigger a custom script when a specific git action occurs, such as every time commit is performed
@@ -166,10 +182,10 @@ A dispensable, insignificant little plug-in, friends who have time can take a lo
     4. How can I ensure that a single cache file does not conflict when collaborating with multi-person?
         - Workaround: use JSONL (JSON Lines) instead of JSON, and with the merge strategy 'merge=union'
 - **Improve**:
-    - Since it has been re-developed, it will be designed in the direction of **excellent products**, and the pursuit of the ultimate **ease of use, simplicity and personalization**
-        - Ease of use: don't let users do things manually if you can, e.g., auto-install Git Hooks, auto-cache, auto-commit, provide customized templates, etc
-        - Simplicity: no unnecessary configurations, the less the simpler, e.g. git account information, repo information, etc., are not required
-        - Personalization: almost everything can be customized, whether it's icons, styles, themes, or features, it's all fully customizable
+    - Since it's a newly developed plugin, it will be designed in the direction of **excellent products**, and the pursuit of the ultimate **ease of use, simplicity and personalization**
+        - **Ease of use**: don't let users do things manually if you can, e.g., auto-install Git Hooks, auto-cache, auto-commit, provide customized templates, etc
+        - **Simplicity**: no unnecessary configuration, no Git dependencies, no CI/CD configuration dependencies, no other package dependencies
+        - **Personalization**: almost everything can be customized, whether it's icons, styles, themes, or features, it's all fully customizable
     - In addition, it has good compatibility and extensibility, and works well in WIN7, mobile devices, old Safari, etc
 - **The Last Secret**:
     - Programming is a hobby, and I'm a marketer of 8 years (Feel free to leave a comment)

{mkdocs_document_dates-3.1.2 → mkdocs_document_dates-3.1.5}/README.md

@@ -8,8 +8,8 @@ An easy-to-use, lightweight MkDocs plugin for displaying the <mark>exact</mark>
 
 ## Features
 
-- Work in any environment, for Git-less environments, CI/CD environments (e.g. GitHub Actions), one-person collaboration, multi-person collaboration, etc
-- Support for manually specifying time and author info in `Front Matter`
+- Always display exact meta-info of the document for any environment (no-Git, Git, all CI/CD build systems, etc)
+- Support for manually specifying time and author in `Front Matter`
 - Support for multiple time formats (date, datetime, timeago)
 - Support for document exclusion mode
 - Flexible display position (top or bottom)
@@ -47,15 +47,14 @@ plugins:
   - document-dates:
       position: top            # Display position: top (after title)  bottom (end of document), default: bottom
       type: date               # Date type: date  datetime  timeago, default: date
-      locale: en               # Localization: zh zh_TW en es fr de ar ja ko ru, default: en
-      date_format: '%Y-%m-%d'  # Date format, Supports all Python datetime format strings, e.g., %Y-%m-%d, %b %d, %Y, etc
-      time_format: '%H:%M:%S'  # Time format (valid only if type=datetime)
+      locale: en               # Localization: en zh zh_TW es fr de ar ja ko ru, default: en
+      date_format: '%Y-%m-%d'  # Date format strings, e.g., %Y-%m-%d, %b %d, %Y, etc
+      time_format: '%H:%M:%S'  # Time format strings (valid only if type=datetime)
       exclude:                 # List of excluded files
         - temp.md              # Exclude specific file
         - private/*            # Exclude all files in private directory, including subdirectories
-        - drafts/*.md          # Exclude all markdown files in the current directory drafts, but not subdirectories
       
-      show_author: true        # Whether to display author: true false, default: true
+      show_author: true        # Show author or not, default: true
 
 ```
 
@@ -63,7 +62,7 @@ plugins:
 
 The plugin will automatically get the exact time of the document, will automatically cache the creation time, but of course, you can also specify it manually in `Front Matter`
 
-Priority: `Front Matter` > `Cache Files` > `File System Timestamps`
+Priority order: `Front Matter` > `Cache Files` > `File System Timestamps`
 
 ```yaml
 ---
@@ -81,7 +80,7 @@ modified: 2025-02-23
 
 The plugin will automatically get the author of the document, will parse the email and make a link, also you can specify it manually in `Front Matter`
 
-Priority: `Front Matter` > `Git Author Info` > `PC Username`
+Priority order: `Front Matter` > `Git Author` > `site_author (mkdocs.yml)` > `PC Username`
 
 ```yaml
 ---
@@ -97,27 +96,42 @@ email: e-name@gmail.com
 
 ## Customization
 
-The plugin supports deep customization, such as icon style, font style, theme color, animation type, dividing line, etc. All of it can be customized by modifying the code in the corresponding file (I've already written the code and comments, you just need to turn on the switch and change the value):
-
-- Style & Theme: `docs/assets/document_dates/user.config.css`
-- Properties & Animations: `docs/assets/document_dates/user.config.js`
-- Localized languages: `docs/assets/document_dates/languages/` , refer to the template file `en.json` for any additions or modifications
-- timeago.js localization: `timeago.min.js` only contains English and Chinese by default, if you need to load other languages, you can configure it as below (choose one):
-    - In user.config.js, refer to [the demo commented out](https://github.com/jaywhj/mkdocs-document-dates/blob/main/mkdocs_document_dates/static/config/user.config.js) at the bottom, translate it into your local language
-    - In mkdocs.yml, add the following two lines to configure the full version of `timeago.full.min.js` to load all languages at once
-    
-        ```yaml
-        extra_javascript:
-          - assets/document_dates/core/timeago.full.min.js
-          - assets/document_dates/core/timeago-load.js
-        ```
+The plugin supports deep customization, such as **icon style, font style, theme color, animation type, dividing line**, etc. All of it can be customized by modifying the preset values in the corresponding file (I've already written the code and comments, you just need to turn on the switch and change the value):
+
+|        Function：        | Location：                               |
+| :----------------------: | ---------------------------------------- |
+|     **Style & Theme**     | `docs/assets/document_dates/user.config.css` |
+| **Properties & Functions** | `docs/assets/document_dates/user.config.js` |
+| **Localized languages** | `docs/assets/document_dates/languages/` <br />refer to the template file `en.json` for any additions or modifications |
+
+**Tip**: when `type: timeago` is set, timeago.js is enabled to render time dynamically, `timeago.min.js` only contains English and Chinese by default, if you need to load other languages, you can configure it as below (choose one):
+
+- In `user.config.js`, refer to [the demo commented out](https://github.com/jaywhj/mkdocs-document-dates/blob/main/mkdocs_document_dates/static/config/user.config.js) at the bottom, translate it into your local language
+- In `mkdocs.yml`, add the following two lines to configure the full version of `timeago.full.min.js` to load all languages at once
+    ```yaml
+    extra_javascript:
+      - assets/document_dates/core/timeago.full.min.js
+      - assets/document_dates/core/timeago-load.js
+    ```
+
+**Demo Images**:
+
+![01-default-w](mkdocs_document_dates/demo_images/01-default-w.png)
+![02-change-icon](mkdocs_document_dates/demo_images/02-change-icon.png)
+![02-change-icon-color](mkdocs_document_dates/demo_images/02-change-icon-color.png)
+![04-default-pop-up](mkdocs_document_dates/demo_images/04-default-pop-up.png)
+![05-change-theme](mkdocs_document_dates/demo_images/05-change-theme.png)
+
+![06-change-theme](mkdocs_document_dates/demo_images/06-change-theme.png)
+![07-pop-up-from-top](mkdocs_document_dates/demo_images/07-pop-up-from-top.png)
+![08-pop-up-from-bottom](mkdocs_document_dates/demo_images/08-pop-up-from-bottom.png)
 
 ## Other Tips
 
-- In order to get the exact creation time, a separate cache file is used to store the creation time of the file, located in the doc folder (hidden by default), please don't delete it:
+- In order to always get the exact creation time, a separate cache file is used to store the creation time of the document, located in the docs folder (hidden by default), please don't delete it:
     - `docs/.dates_cache.jsonl`, cache file
-    - `docs/.gitattributes`, merge mechanism for cache file in case of multi-person collaboration
-- The Git Hooks mechanism is used to automatically trigger the storing of the cache (every time executes a git commit), and the cached file is automatically committed along with it. In addition, the installation of Git Hooks is automatically triggered when the plugin is installed, without any manual intervention!
+    - `docs/.gitattributes`, merge mechanism for cache file
+- The Git Hooks mechanism is used to automatically trigger the storing of the cache (on each git commit), and the cached file is automatically committed along with it, in addition, the installation of Git Hooks is automatically triggered when the plugin is installed, without any manual intervention!
 
 <br />
 
@@ -126,11 +140,11 @@ The plugin supports deep customization, such as icon style, font style, theme co
 A dispensable, insignificant little plug-in, friends who have time can take a look \^\_\^ 
 
 - **Origin**:
-    - Because [mkdocs-git-revision-date-localized-plugin](https://github.com/timvink/mkdocs-git-revision-date-localized-plugin), a great project. When I used it at the end of 2024, I found that I couldn't use it locally because my mkdocs documentation was not included in git management, then I don't understand why not read the file system time, but to use the git time, and raised an issue to the author, but didn't get a reply for about a week (the author had a reply later, nice guy, I guess he was busy at the time), and then I thought, there is nothing to do during the Chinese New Year, and now AI is so hot, why not with the help of the AI try it out for myself, it was born, born in February 2025
+    - Because [mkdocs-git-revision-date-localized-plugin](https://github.com/timvink/mkdocs-git-revision-date-localized-plugin), a great project. When I used it at the end of 2024, I found that I couldn't use it locally because my mkdocs documentation was not included in git management, I don't understand why not read the file system time, but to use the git time, and the filesystem time is more accurate, then raised an issue to the author, but didn't get a reply for about a week (the author had a reply later, nice guy, I guess he was busy at the time), and then I thought, there is nothing to do during the Chinese New Year, and now AI is so hot, why not with the help of the AI try it out for myself, it was born, born in February 2025
 - **Iteration**:
     - After development, I understood why not use filesystem time, because files will be rebuilt when they go through git checkout or clone, resulting in the loss of original timestamp information, and there are many solutions:
     - Method 1: Use the last git commit time as the last update time, and the first git commit time as the creation (there is a margin of error, but it's acceptable), mkdocs-git-revision-date-localized-plugin does this
-    - Method 2: You can cache the original time, and then read the cache subsequently. The cache can be in Front Matter of the source document or in a separate file, I chose the latter. Storing in Front Matter makes sense and is simple, but this will modify the source content of the document, although it doesn't have any impact on the body, but I still want to ensure the originality of the data!
+    - Method 2: You can cache the original time in advance, and then read the cache subsequently. The cache can be in Front Matter of the source document or in a separate file, I chose the latter. Storing in Front Matter makes sense and is easier, but this will modify the source content of the document, although it doesn't have any impact on the body, but I still want to ensure the originality of the data!
 - **Difficulty**:
     1. When to read and store original time? This is just a plugin for mkdocs, with very limited access and permissions, mkdocs provides only build and serve, so in case a user commits directly without executing build or serve (e.g., when using a CI/CD build system), then you won't be able to retrieve the time information of the file, not to mention caching it!
         - Let's take a straight shot: the Git Hooks mechanism was found, prompted by the AI, which can trigger a custom script when a specific git action occurs, such as every time commit is performed
@@ -141,10 +155,10 @@ A dispensable, insignificant little plug-in, friends who have time can take a lo
     4. How can I ensure that a single cache file does not conflict when collaborating with multi-person?
         - Workaround: use JSONL (JSON Lines) instead of JSON, and with the merge strategy 'merge=union'
 - **Improve**:
-    - Since it has been re-developed, it will be designed in the direction of **excellent products**, and the pursuit of the ultimate **ease of use, simplicity and personalization**
-        - Ease of use: don't let users do things manually if you can, e.g., auto-install Git Hooks, auto-cache, auto-commit, provide customized templates, etc
-        - Simplicity: no unnecessary configurations, the less the simpler, e.g. git account information, repo information, etc., are not required
-        - Personalization: almost everything can be customized, whether it's icons, styles, themes, or features, it's all fully customizable
+    - Since it's a newly developed plugin, it will be designed in the direction of **excellent products**, and the pursuit of the ultimate **ease of use, simplicity and personalization**
+        - **Ease of use**: don't let users do things manually if you can, e.g., auto-install Git Hooks, auto-cache, auto-commit, provide customized templates, etc
+        - **Simplicity**: no unnecessary configuration, no Git dependencies, no CI/CD configuration dependencies, no other package dependencies
+        - **Personalization**: almost everything can be customized, whether it's icons, styles, themes, or features, it's all fully customizable
     - In addition, it has good compatibility and extensibility, and works well in WIN7, mobile devices, old Safari, etc
 - **The Last Secret**:
     - Programming is a hobby, and I'm a marketer of 8 years (Feel free to leave a comment)

{mkdocs_document_dates-3.1.2 → mkdocs_document_dates-3.1.5}/mkdocs_document_dates/cache_manager.py

@@ -13,13 +13,13 @@ logging.basicConfig(
 )
 
 def find_mkdocs_projects():
+    projects = []
     try:
         git_root = Path(subprocess.check_output(
             ['git', 'rev-parse', '--show-toplevel'],
             text=True, encoding='utf-8'
         ).strip())
 
-        projects = []
         # 遍历 git_root 及子目录, 寻找 mkdocs.yml 文件
         for config_file in git_root.rglob('mkdocs.y*ml'):
             if config_file.name.lower() in ('mkdocs.yml', 'mkdocs.yaml'):
@@ -27,13 +27,12 @@ def find_mkdocs_projects():
 
         if not projects:
             logging.info("No MkDocs projects found in the repository")
-        return projects
     except subprocess.CalledProcessError as e:
         logging.error(f"Failed to find the Git repository root: {e}")
-        return []
     except Exception as e:
         logging.error(f"Unexpected error while searching for MkDocs projects: {e}")
-        return []
+    
+    return projects
 
 def get_file_creation_time(file_path):
     try:
@@ -57,9 +56,9 @@ def get_git_first_commit_time(file_path):
         # git log --reverse --format="%aI" --date=iso -- {file_path} | head -n 1
         result = subprocess.run(['git', 'log', '--reverse', '--format=%aI', '--', file_path], capture_output=True, text=True)
         if result.returncode == 0:
-            commits = result.stdout.strip().split('\n')
-            if commits and commits[0]:
-                return datetime.fromisoformat(commits[0]).replace(tzinfo=None)
+            first_line = result.stdout.partition('\n')[0].strip()
+            if first_line:
+                return datetime.fromisoformat(first_line).replace(tzinfo=None)
     except Exception as e:
         logging.info(f"Error getting git first commit time for {file_path}: {e}")
     return None
@@ -164,7 +163,7 @@ def update_cache():
                 cmd = ["git", "ls-files", "*.md"]
                 result = subprocess.run(cmd, cwd=docs_dir, capture_output=True, text=True, check=True)
                 tracked_files = result.stdout.splitlines() if result.stdout else []
-                
+
                 if not tracked_files:
                     logging.info(f"No tracked markdown files found in {docs_dir}")
                     continue
@@ -176,17 +175,17 @@ def update_cache():
                 # 读取新的JSONL缓存文件（如果存在）
                 jsonl_cache_file = docs_dir / '.dates_cache.jsonl'
                 jsonl_dates_cache = read_jsonl_cache(jsonl_cache_file)
-                
+
                 # 根据 git已跟踪的文件来更新
                 for file_path in tracked_files:
                     try:
                         rel_path = file_path
                         full_path = docs_dir / rel_path
-                        
+
                         # 如果文件已在JSONL缓存中，跳过
                         if rel_path in jsonl_dates_cache:
                             continue
-                        
+
                         # 处理新文件或迁移旧JSON缓存
                         if rel_path in json_dates_cache:
                             jsonl_dates_cache[rel_path] = json_dates_cache[rel_path]

{mkdocs_document_dates-3.1.2 → mkdocs_document_dates-3.1.5}/mkdocs_document_dates/hooks/pre-commit

@@ -1,10 +1,9 @@
 #!/usr/bin/env python3
 
-import sys
-
 try:
     from mkdocs_document_dates.cache_manager import update_cache
-except ImportError:
+except Exception:
+    import sys
     # 正常退出（0 状态码），不影响 git 的后续动作
     sys.exit(0)
 

{mkdocs_document_dates-3.1.2 → mkdocs_document_dates-3.1.5}/mkdocs_document_dates/hooks_installer.py

@@ -23,7 +23,7 @@ def check_python_version(interpreter):
             [interpreter, "-c", "import sys; print(sys.version_info >= (3, 7))"],
             capture_output=True, text=True, check=False
         )
-        if result.returncode == 0 and result.stdout.strip() == 'True':
+        if result.returncode == 0 and result.stdout.strip().lower() == 'true':
             return True
         else:
             logging.warning(f"Low python version, requires python_requires >=3.7")