[PR #60] [CLOSED] fix: read CLI version from package.json instead of hardcoded value #279

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/60
Author: @southpolesteve
Created: 2/25/2026
Status: ❌ Closed

Base: main ← Head: fix/cli-version

📝 Commits (2)

e4648dc ci: commit version bump back to main after publish
6920bf0 fix: read CLI version from package.json instead of hardcoded value

📊 Changes

2 files changed (+11 additions, -4 deletions)

View changed files

📝 .github/workflows/publish.yml (+8 -3)
📝 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.

_{🔄 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/60 **Author:** [@southpolesteve](https://github.com/southpolesteve) **Created:** 2/25/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/cli-version` --- ### 📝 Commits (2) - [`e4648dc`](https://github.com/cloudflare/vinext/commit/e4648dc62c1fcde938c971fed21ca6abaed6759b) ci: commit version bump back to main after publish - [`6920bf0`](https://github.com/cloudflare/vinext/commit/6920bf0324858fef433a6bcea1a698f8efa568ab) fix: read CLI version from package.json instead of hardcoded value ### 📊 Changes **2 files changed** (+11 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/publish.yml` (+8 -3) 📝 `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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>