Inconsistent journal `block/name` format after upgrade to 20260508
@tiensonqin is already working on this.
Since Jun 2, 2026.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
### Search first
- [x] I searched and no similar issues were found
### What Happened?
I have date format as "yyyy-MM-dd".
I did upgrade at April 30th, May 9th, May 10th, May 18th.
* 2.0.1-alpha+nightly.20260429 [62eac11](https://github.com/logseq/logseq/commit/62eac11fe34e71915a19588db04996944c098dbe)
* 2.0.1-alpha+nightly.20260508 [427dbe3](https://github.com/logseq/logseq/commit/427dbe3f58984f9a431c1e9e807383e3ba88657f)
* 2.0.1-alpha+nightly.20260510 [1f9c017](https://github.com/logseq/logseq/commit/1f9c017998e1472f413165c30e6df08663338ab1)
* 2.0.1-alpha+nightly.20260515 [302f798](https://github.com/logseq/logseq/commit/302f79805220cefab26da66eae1e18c69e165afb)
Now I find my journal before May 9th has `block/name` like "2026-05-09", while the journal since May 10th is "may 10th, 2026".
The `block/title` keeps in the same format as my setting.
This seems break plugin API like `getPage()` and `pushState()` when the journal date "2026-05-18" is input parameter. And my plugin fails to work.
### Reproduce the Bug
1. Install 2.0.1-alpha+nightly.20260429 [62eac11](https://github.com/logseq/logseq/commit/62eac11fe34e71915a19588db04996944c098dbe) and create a journal page.
2. Upgrade to new version and create another journal page.
3. Check the page data of both journals. The `block/name` is in different format.
### Expected Behavior
_No response_
### Screenshots
### Files
_No response_
### Browser, Desktop or Mobile Platform Information
* April 30th: 2.0.1-alpha+nightly.20260429 [62eac11](https://github.com/logseq/logseq/commit/62eac11fe34e71915a19588db04996944c098dbe)
* May 9th: 2.0.1-alpha+nightly.20260508 [427dbe3](https://github.com/logseq/logseq/commit/427dbe3f58984f9a431c1e9e807383e3ba88657f)
* May 10th: 2.0.1-alpha+nightly.20260510 [1f9c017](https://github.com/logseq/logseq/commit/1f9c017998e1472f413165c30e6df08663338ab1)
* May 18th: 2.0.1-alpha+nightly.20260515 [302f798](https://github.com/logseq/logseq/commit/302f79805220cefab26da66eae1e18c69e165afb)
### Additional Context
_No response_
### Are you willing to submit a PR? If you know how to fix the bug.
- [ ] I'm willing to submit a PR (Thank you!)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.