Skip to content

feat: use UTC dates for create-vue releases - #1183

Open
haoqunjiang wants to merge 4 commits into
vuejs:mainfrom
haoqunjiang:codex/utc-release-versions
Open

haoqunjiang wants to merge 4 commits into
vuejs:mainfrom
haoqunjiang:codex/utc-release-versions

Conversation

@haoqunjiang

@haoqunjiang haoqunjiang commented Nov 11, 2026 •

Copy link
Copy Markdown
Member

Each create-vue release captures the templates and tooling we recommend for new Vue projects at the time. We already include the release date in GitHub release titles. Putting it in the npm version makes it visible in a bug report or a pinned command, and saves maintainers from deciding whether a template update warrants a minor or patch bump.

With this change, running pnpm release on November 11, 2026 produces 3.20261111.0. A second release on the same UTC day gets 3.20261111.1. Keeping the leading 3 lets npm create vue@3 follow Vue 3 template updates. If we move to Vue 4, that command can continue to resolve to the final Vue 3 scaffolder.

The welcome banner reads the UTC release date from the version and formats it for the user’s locale. For example, British English users see Released 11 Nov 2026 (UTC). The full version is available through --version.

@haoqunjiang haoqunjiang self-assigned this Nov 11, 2026

@btea btea left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://e18e.dev/docs/replacements/semver Maybe we can replace semver with verkit.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants