Auto update date when markdown modified not follow isModifiedDate date pattern on GitHub Codespaces #642

New Issue

Closed

opened 2026-10-05 02:58:11 +02:00 by adam · 9 comments

adam commented 2026-10-05 02:58:11 +02:00

Owner

Copy link

Copy source

Describe the bug
Auto update modified date not follow configuration isModifiedDate

To Reproduce
Steps to reproduce the behavior:

1. Setup frontmatter.json

{
  "$schema": "https://frontmatter.codes/frontmatter.schema.json",
  "frontMatter.content.autoUpdateDate": true,
  "frontMatter.preview.host": "http://localhost:4000",
  "frontMatter.taxonomy.contentTypes": [
    {
      "name": "default",
      "pageBundle": false,
      "fields": [
        {
          "title": "Title",
          "name": "title",
          "type": "string"
        },
        {
          "title": "Description",
          "name": "description",
          "type": "string"
        },
        {
          "title": "Publishing date",
          "name": "date",
          "type": "datetime",
          "default": "{{now}}",
          "isPublishDate": true,
          "dateFormat": "yyyy-MM-dd'T'HH:mm:ssXXX"
        },
        {
          "title": "Thumbnail",
          "name": "thumbnail",
          "type": "image"
        },
        {
          "title": "Is in draft",
          "name": "draft",
          "type": "boolean"
        },
        {
          "title": "Tags",
          "name": "tags",
          "type": "tags"
        },
        {
          "title": "Categories",
          "name": "categories",
          "type": "categories"
        },
        {
          "title": "updated",
          "name": "updated",
          "type": "datetime",
          "default": "{{now}}",
          "isModifiedDate": true,
          "dateFormat": "yyyy-MM-dd'T'HH:mm:ssXXX"
        },
        {
          "name": "permalink",
          "editable": true,
          "type": "slug"
        },
        {
          "title": "Author",
          "name": "author",
          "type": "divider"
        }
      ]
    }
  ],
  "frontMatter.framework.id": "hexo",
  "frontMatter.content.publicFolder": "hexo:post_asset_folder",
  "frontMatter.content.pageFolders": [
    {
      "path": "[[workspace]]/posts",
      "title": "Source Posts"
    }
  ],
  "frontMatter.site.baseURL": "https://www.webmanajemen.com/"
}

2. Open markdown frontmatter file format
3. Edit any text then save

Expected behavior
The modified date should follow format this config

{
  "title": "updated",
  "name": "updated",
  "type": "datetime",
  "default": "{{now}}",
  "isModifiedDate": true,
  "dateFormat": "yyyy-MM-dd'T'HH:mm:ssXXX"
}

looks like 2024-06-01T17:14:14+07:00 - hexo date format issue

Screenshots

look at updated: 2024-06-02T00:02:57Z, it totally wrong and hexo will produce invalid date format.

Desktop (please complete the following information):

• OS: Ubuntu (Codespace), Windows 10 (PC)
• Browser: Firefox latest
• Version: idk

**Describe the bug** Auto update modified date not follow configuration `isModifiedDate` **To Reproduce** Steps to reproduce the behavior: 1. Setup `frontmatter.json` ```jsonc { "$schema": "https://frontmatter.codes/frontmatter.schema.json", "frontMatter.content.autoUpdateDate": true, "frontMatter.preview.host": "http://localhost:4000", "frontMatter.taxonomy.contentTypes": [ { "name": "default", "pageBundle": false, "fields": [ { "title": "Title", "name": "title", "type": "string" }, { "title": "Description", "name": "description", "type": "string" }, { "title": "Publishing date", "name": "date", "type": "datetime", "default": "{{now}}", "isPublishDate": true, "dateFormat": "yyyy-MM-dd'T'HH:mm:ssXXX" }, { "title": "Thumbnail", "name": "thumbnail", "type": "image" }, { "title": "Is in draft", "name": "draft", "type": "boolean" }, { "title": "Tags", "name": "tags", "type": "tags" }, { "title": "Categories", "name": "categories", "type": "categories" }, { "title": "updated", "name": "updated", "type": "datetime", "default": "{{now}}", "isModifiedDate": true, "dateFormat": "yyyy-MM-dd'T'HH:mm:ssXXX" }, { "name": "permalink", "editable": true, "type": "slug" }, { "title": "Author", "name": "author", "type": "divider" } ] } ], "frontMatter.framework.id": "hexo", "frontMatter.content.publicFolder": "hexo:post_asset_folder", "frontMatter.content.pageFolders": [ { "path": "[[workspace]]/posts", "title": "Source Posts" } ], "frontMatter.site.baseURL": "https://www.webmanajemen.com/" } ``` 2. Open markdown frontmatter file format 3. Edit any text then save **Expected behavior** The modified date should follow format this config ```jsonc { "title": "updated", "name": "updated", "type": "datetime", "default": "{{now}}", "isModifiedDate": true, "dateFormat": "yyyy-MM-dd'T'HH:mm:ssXXX" } ``` looks like `2024-06-01T17:14:14+07:00` - [hexo date format issue](https://github.com/estruyf/vscode-front-matter/issues/736) **Screenshots** look at `updated: 2024-06-02T00:02:57Z`, it totally wrong and `hexo` will produce invalid date format.  **Desktop (please complete the following information):** - OS: Ubuntu (Codespace), Windows 10 (PC) - Browser: Firefox latest - Version: idk <!-- github-sync-id:2329399174 -->

adam closed this issue 2026-10-05 02:58:11 +02:00

adam commented 2026-10-05 02:58:12 +02:00

Author

Owner

Copy link

Copy source

That is weird, as the date formatting uses the dateFormat setting in the code. Which version of FM are you using? I cannot reproduce it with your configuration in the stable or beta versions.

https://github.com/estruyf/vscode-front-matter/assets/2900833/9ab1faf5-954b-40af-b692-34d1cae44116

That is weird, as the date formatting uses the `dateFormat` setting in the code. Which version of FM are you using? I cannot reproduce it with your configuration in the stable or beta versions. https://github.com/estruyf/vscode-front-matter/assets/2900833/9ab1faf5-954b-40af-b692-34d1cae44116 <!-- github-comment-id:2151835107 -->

adam commented 2026-10-05 02:58:13 +02:00

Author

Owner

Copy link

Copy source

That is weird, as the date formatting uses the dateFormat setting in the code. Which version of FM are you using? I cannot reproduce it with your configuration in the stable or beta versions.

version latest stable. here my screen record - https://drive.google.com/file/d/1n5mbJC9ihCSM1jSxaGMGUdyn3I0FASxY/view?usp=sharing

> That is weird, as the date formatting uses the `dateFormat` setting in the code. Which version of FM are you using? I cannot reproduce it with your configuration in the stable or beta versions. version latest stable. here my screen record - https://drive.google.com/file/d/1n5mbJC9ihCSM1jSxaGMGUdyn3I0FASxY/view?usp=sharing <!-- github-comment-id:2153603571 -->

adam commented 2026-10-05 02:58:13 +02:00

Author

Owner

Copy link

Copy source

@estruyf here my full project https://github.com/dimaslanjaka/source-posts/tree/master (branch master and dont forget git submodule update -i -r)
You can check which parts cause bugs.

@estruyf here my full project https://github.com/dimaslanjaka/source-posts/tree/master (branch master and dont forget `git submodule update -i -r`) You can check which parts cause bugs. <!-- github-comment-id:2153613084 -->

adam commented 2026-10-05 02:58:14 +02:00

Author

Owner

Copy link

Copy source

Interesting. I cannot reproduce it locally; it is only in a codespace. Will have to find a way how I can test it 🙃

Interesting. I cannot reproduce it locally; it is only in a codespace. Will have to find a way how I can test it 🙃 <!-- github-comment-id:2154242030 -->

adam commented 2026-10-05 02:58:15 +02:00

Author

Owner

Copy link

Copy source

🤦‍♂️ - there is nothing wrong; it is just that the Codespaces clock is set to UTC. That is why the XXX results in Z.

So the yyyy-MM-dd'T'HH:mm:ssXXX format on a Codespace is formatted to: 2024-06-07T08:02:21Z.

You can also see this in the date-fns its format method documentation: https://date-fns.org/v3.6.0/docs/format - XXX results in: -08:00, +05:30, Z

Also checked with extra logging in the output:

Here you can see that the dateFormat value is used for formatting your date.

🤦‍♂️ - there is nothing wrong; it is just that the Codespaces clock is set to UTC. That is why the `XXX` results in `Z`. So the `yyyy-MM-dd'T'HH:mm:ssXXX` format on a Codespace is formatted to: `2024-06-07T08:02:21Z`. You can also see this in the `date-fns` its `format` method documentation: https://date-fns.org/v3.6.0/docs/format - `XXX` results in: -08:00, +05:30, Z Also checked with extra logging in the output:  Here you can see that the `dateFormat` value is used for formatting your date. <!-- github-comment-id:2154317555 -->

adam commented 2026-10-05 02:58:15 +02:00

Author

Owner

Copy link

Copy source

🤦‍♂️ - there is nothing wrong; it is just that the Codespaces clock is set to UTC. That is why the XXX results in Z.

So the yyyy-MM-dd'T'HH:mm:ssXXX format on a Codespace is formatted to: 2024-06-07T08:02:21Z.

You can also see this in the date-fns its format method documentation: https://date-fns.org/v3.6.0/docs/format - XXX results in: -08:00, +05:30, Z

Also checked with extra logging in the output:

Here you can see that the dateFormat value is used for formatting your date.

when I tap Update NOW working (auto update post date disabled state)

only the auto update modified post wrong format

> 🤦‍♂️ - there is nothing wrong; it is just that the Codespaces clock is set to UTC. That is why the `XXX` results in `Z`. > > So the `yyyy-MM-dd'T'HH:mm:ssXXX` format on a Codespace is formatted to: `2024-06-07T08:02:21Z`. > > You can also see this in the `date-fns` its `format` method documentation: https://date-fns.org/v3.6.0/docs/format - `XXX` results in: -08:00, +05:30, Z > > Also checked with extra logging in the output: > >  > > Here you can see that the `dateFormat` value is used for formatting your date. when I tap **Update NOW** working (auto update post date disabled state)  only the auto update modified post wrong format <!-- github-comment-id:2164039698 -->

adam commented 2026-10-05 02:58:16 +02:00

Author

Owner

Copy link

Copy source

When you click on the now button, your browser triggers it, invoking it from the client side, which results in a correct value on your end.

When the automated date update gets invoked, it is on the "backend", which runs on the codespace itself. Because the codespace runs on UTC, it returns a different value.

When you click on the `now` button, your browser triggers it, invoking it from the client side, which results in a correct value on your end. When the automated date update gets invoked, it is on the "backend", which runs on the codespace itself. Because the codespace runs on UTC, it returns a different value. <!-- github-comment-id:2165069904 -->

adam commented 2026-10-05 02:58:17 +02:00

Author

Owner

Copy link

Copy source

@dimaslanjaka I found a solution and it is to set the timezone for your GH Codespace. I just wrote a blog post about it on how you can set the timezone for your codespace: https://www.eliostruyf.com/set-timezone-github-codespaces/

@dimaslanjaka I found a solution and it is to set the timezone for your GH Codespace. I just wrote a blog post about it on how you can set the timezone for your codespace: https://www.eliostruyf.com/set-timezone-github-codespaces/ <!-- github-comment-id:2165516065 -->

adam commented 2026-10-05 02:58:17 +02:00

Author

Owner

Copy link

Copy source

@dimaslanjaka I found a solution and it is to set the timezone for your GH Codespace. I just wrote a blog post about it on how you can set the timezone for your codespace: https://www.eliostruyf.com/set-timezone-github-codespaces/

nice working.

here my step to get working (might useful for someone else):

• set timezone in .devcontainer/devcontainer.json => https://github.com/dimaslanjaka/source-posts/blob/d67d837dfc29f57b5f2e43cc9d264486a98c605e/.devcontainer/devcontainer.json#L1-L5
• add timezone change script in dotfiles repository

# timezone.sh
#!/bin/bash

# Set timezone to Asia/Jakarta
sudo ln -sf /usr/share/zoneinfo/Asia/Jakarta /etc/localtime
sudo timedatectl set-timezone Asia/Jakarta
echo "Timezone set to $(date)"

• include the timezone script in .bashrc or .zshrc

# your other .bashrc or .zshrc configs

# set timezone
if [ -f ~/dotfiles/timezone.sh ]; then
    chmod +x ~/dotfiles/timezone.sh
    ~/dotfiles/timezone.sh
elif [ -f ./timezone.sh ]; then
    chmod +x ./timezone.sh
    ./timezone.sh
fi

• now rebuild your codespaces
• after finish, open terminal execute command date

> @dimaslanjaka I found a solution and it is to set the timezone for your GH Codespace. I just wrote a blog post about it on how you can set the timezone for your codespace: https://www.eliostruyf.com/set-timezone-github-codespaces/ nice working.  here my step to get working (might useful for someone else): - set timezone in `.devcontainer/devcontainer.json` => https://github.com/dimaslanjaka/source-posts/blob/d67d837dfc29f57b5f2e43cc9d264486a98c605e/.devcontainer/devcontainer.json#L1-L5 - add timezone change script in dotfiles repository ```bash # timezone.sh #!/bin/bash # Set timezone to Asia/Jakarta sudo ln -sf /usr/share/zoneinfo/Asia/Jakarta /etc/localtime sudo timedatectl set-timezone Asia/Jakarta echo "Timezone set to $(date)" ``` - include the timezone script in `.bashrc` or `.zshrc` ```bash # your other .bashrc or .zshrc configs # set timezone if [ -f ~/dotfiles/timezone.sh ]; then chmod +x ~/dotfiles/timezone.sh ~/dotfiles/timezone.sh elif [ -f ./timezone.sh ]; then chmod +x ./timezone.sh ./timezone.sh fi ``` - now rebuild your codespaces - after finish, open terminal execute command `date` <!-- github-comment-id:2166938052 -->

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

beta

dependabot/npm_and_yarn/js-yaml-4.3.1

dependabot/npm_and_yarn/multi-7958ac4c45

dependabot/npm_and_yarn/postcss-8.5.25

dependabot/npm_and_yarn/multi-670d462a53

dependabot/npm_and_yarn/http-proxy-middleware-2.0.10

dependabot/npm_and_yarn/shell-quote-1.10.0

dependabot/npm_and_yarn/websocket-driver-0.7.5

dependabot/npm_and_yarn/multi-6aaed2ab8e

copilot/validate-issue-1043

dependabot/npm_and_yarn/multi-84120a5570

dependabot/npm_and_yarn/launch-editor-2.14.1

dependabot/npm_and_yarn/multi-9dd3b9b346

estruyf/smart-file-rename

copilot/fix-unwanted-auto-update-publish-date

copilot/fix-content-view-sorting-issue

copilot/fix-virtual-workspace-folder-selection

copilot/fix-937

copilot/fix-965

copilot/fix-958

copilot/fix-950

copilot/fix-932

copilot-integration

hotfix/10.2.1

issue/816

issue/671

i18n

azure-translator

issue/747

issue/673

poc/content-tagging

combobox

v10.13.0

v10.12.0

v10.11.0

v10.10.1

v10.10.0

v10.9.0

v10.8.0

v10.7.0

v10.6.0

v10.5.1

v10.5.0

v10.4.1

v10.4.0

v10.3.0

v10.2.1

v10.2.0

v10.1.0

v10.0.2

v10.0.1

v10.0.0

v9.4.0

v9.3.1

v9.3.0

v9.2.0

v9.1.0

v9.0.0

v8.4.0

v8.3.0

v8.2.0

v8.1.2

v8.1.1

v8.1.0

v8.0.1

v8.0.0

v7.3.4

v7.3.3

v7.3.2

v7.3.1

v7.3.0

v7.2.0

v7.1.2

v7.1.1

v7.1.0

v7.0.0

v6.1.1

v6.1.0

v6.0.0

v5.10.0

v5.9.0

v5.8.0

v5.7.0

v5.6.0

v5.5.0

v5.4.0

v5.3.1

v5.3.0

v5.2.0

v5.1.1

v5.1.0

v5.0.0

4.0.1

4.0.0

3.1.0

v3.0.2

v3.0.1

v3.0.0

v2.5.1

v2.5.0

v2.4.1

v2.4.0

v2.3.0

v2.2.0

v2.1.0

v2.0.1

v2.0.0

v1.18.0

v1.17.1

v1.17.0

v1.16.1

v1.16.0

v1.15.1

v1.15.0

Labels

No items

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

adam (Adam Wojcieszonek)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/vscode-front-matter#642