Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.

This PR stops forcefully converting the last modified date into UTC to respect Hugo's timeZone configuration.

As described in #249 (comment), I understand this will be a breaking change. If we should keep backward compatibility, I will open another PR to introduce params.forceUTCInLastMod (key name is subject to discuss).

Test plan

No particular test plan because the change is small. I checked in my local as below:

• config.yaml:

  timeZone: Asia/Tokyo
  params:
    dateFormat: January 2, 2006 at 3:04 PM MST
    shortDateFormat: 15:04 MST — Jan 2
    enableLastMod: true

• last modified info in git:

  ❯ git --no-pager log -1 content/issues/2022-10-27-sample-issue.md
  commit 4b...masked....14
  Author: ...masked....
  Date:   Thu Oct 27 20:07:33 2022 +0900

Then, rendered fotter was:

Closing issues

closes #248