Change:
append(moreInfoContainer, $('.additional-details-title', undefined, localize('Marketplace Info', "More Info"))); const moreInfo = append(moreInfoContainer, $('.more-info')); if (gallery) { <ins> const pub = new Date(gallery.releaseDate); const last_rel = new Date(gallery.lastUpdated); </ins> append(moreInfo, $('.more-info-entry', undefined, $('div', undefined, localize('published', "Published")), <del> $('div', undefined, new Date(gallery.releaseDate).toLocaleString(language, { hourCycle: 'h23' })) </del> <ins> $('div', undefined, [pub.getFullYear(), pub.getMonth() + 1, pub.getDate()].join('-').concat(', ' + pub.toLocaleTimeString(language, { hourCycle: 'h23' }))) </ins> ), $('.more-info-entry', undefined, $('div', undefined, localize('last released', "Last released")), <del> $('div', undefined, new Date(gallery.lastUpdated).toLocaleString(language, { hourCycle: 'h23' })) </del> <ins> $('div', undefined, [last_rel.getFullYear(), last_rel.getMonth() + 1, last_rel.getDate()].join('-').concat(', ' + last_rel.toLocaleTimeString(language, { hourCycle: 'h23' }))) </ins> ) ); } if (extension.local && extension.local.installedTimestamp) { <ins> const last_up = new Date(extension.local.installedTimestamp); </ins> append(moreInfo, $('.more-info-entry', undefined, $('div', undefined, localize('last updated', "Last updated")), <del> $('div', undefined, new Date(extension.local.installedTimestamp).toLocaleString(language, { hourCycle: 'h23' })) </del> <ins> $('div', undefined, [last_up.getFullYear(), last_up.getMonth() + 1, last_up.getDate()].join('-').concat(', ' + last_up.toLocaleTimeString(language, { hourCycle: 'h23' }))) </ins> ) ); }

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: Version: 1.78.1 OS Version: macOS 12.6.3 (21G419) Steps to Reproduce: your OS date format to . the Extensions pane. on an extension. The dates in "More Info" are shown in dd/mm/yyyy format. VSCode should have a setting where the locale can be set, but should use the system locale if it has not been set. (I assume there is no setting; a search for "locale" doesn't find anything, and "date" or "language" produces far too many results to be useful!) Alternatively, if implementing locale support here is tricky, yyyy-mm-dd could be used — or just text like "July 11, 2016" rather than short dates. The dates are shown in mm/dd/yyyy format, despite the fact that most locales do not use this format. Here's an example, grabbed today (May 10, 2023). The "last release" and "last updated" dates give a clue in this case, as it's not yet September or October, but the "published" date looks valid. However, it's July 11, 2016 and not November 7, 2016. !
These dates are shown based on VS Code Display Language / Locale. Changing this will change the format.
! please explain what I need to do to have my VS Code display in English but with "rest of the world" date ordering rather than US ordering.
Not sure what is recommended here. I am using to display this date string.

If one changes the locale to , language is not picking up this. Please suggest what is recommended.
There's no such thing as in VS Code. We only support ... which basically defaults to . Couple of options: use so everyone is happy (simplest) look at which will be exactly what the user has in , but then you are going against what the language was resolved to which is ... (aka simple, but risky...) we ship an en-GB language pack... (not simple... also ) Ah... there's a comment in that issue about this:
If there's no such thing as (very annoying that the US seems to think their version of English is the One True Version, rather than the one spoken in England — but I understand the reason behind removing the language pack) then ISO-format dates would be least confusing for all.
I'd like to help with this but I keep getting thrown errors when attempting to download the dependencies for the repo with yarn so I can't test my code. I already made changes in my repo that might fix this issue but I can't test it
I would love to help with the issue, Can you guide me what exactly needs to be done, are we going with "2020/10/20" this format? and where should we do change this?
Yes
To add to this, I believe there is already a toISOString method that can be used to convert the published, last released, and last updated dates to the ISO format. I still ran into errors when I tried to setup the environment to test my code, which is why I haven't submitted a pull request. If someone can properly test the code and confirm that it works, then they can submit a PR if they want. Otherwise, I'll submit a PR if/when I get my setup working and can test my proposed solution.
Hey I was looking into this issue and implemented the format. I received the following output and wanted to confirm if it's correct: !
This looks good
Based on the separators should be - rather than /