[PR #61] [MERGED] fix: read CLI version from package.json instead of hardcoded value #280

New issue

Closed

opened 2026-05-06 12:38:56 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 12:38:56 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/cloudflare/vinext/pull/61
Author: @southpolesteve
Created: 2/25/2026
Status: ✅ Merged
Merged: 2/25/2026
Merged by: @southpolesteve

Base: main ← Head: fix/cli-version-clean

📝 Commits (1)

2a58ee9 fix: read CLI version from package.json instead of hardcoded value

📊 Changes

1 file changed (+3 additions, -1 deletions)

View changed files

📝 packages/vinext/src/cli.ts (+3 -1)

📄 Description

Summary

The CLI help and --version output was hardcoded to v0.0.1 — now reads from package.json at runtime so it always matches the published version.

Note: for users installing from npm this works immediately (the published tarball has the correct version in package.json). For the git repo to stay in sync, we'll need a separate PR to wire up the version commit-back in the publish workflow.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/cloudflare/vinext/pull/61 **Author:** [@southpolesteve](https://github.com/southpolesteve) **Created:** 2/25/2026 **Status:** ✅ Merged **Merged:** 2/25/2026 **Merged by:** [@southpolesteve](https://github.com/southpolesteve) **Base:** `main` ← **Head:** `fix/cli-version-clean` --- ### 📝 Commits (1) - [`2a58ee9`](https://github.com/cloudflare/vinext/commit/2a58ee9e43280fe80ebb1234dbd02f2a32c15a19) fix: read CLI version from package.json instead of hardcoded value ### 📊 Changes **1 file changed** (+3 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `packages/vinext/src/cli.ts` (+3 -1) </details> ### 📄 Description ## Summary - The CLI help and `--version` output was hardcoded to `v0.0.1` — now reads from `package.json` at runtime so it always matches the published version. Note: for users installing from npm this works immediately (the published tarball has the correct version in package.json). For the git repo to stay in sync, we'll need a separate PR to wire up the version commit-back in the publish workflow. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>