Skip to content

QVAC-13104 feat: Add cli shim package for npx qvac support - #229

Closed
opaninakuffo wants to merge 3 commits into
tetherto:mainfrom
opaninakuffo:feat/qvac-shim-package
Closed

opaninakuffo wants to merge 3 commits into
tetherto:mainfrom
opaninakuffo:feat/qvac-shim-package

Conversation

@opaninakuffo

@opaninakuffo opaninakuffo commented Feb 10, 2026

Copy link
Copy Markdown
Contributor

🎯 What problem does this PR solve?

  • Users must run npx @qvac/cli — scoped names are cumbersome
  • No way to simply run npx qvac

📝 How does it solve it?

Introduces packages/qvac — an unscoped shim that forwards to @qvac/cli:

  • Thin forwarder — spawns CLI with all args passed through
  • Auto-updates — caret dependency (^0.1.x) picks up patches automatically
  • NPM-only workflow — no GPR, publishes only on release-* branches

Usage (after publishing)

npx qvac bundle sdk

@opaninakuffo opaninakuffo changed the title feat: add cli shim package for npx qvac support QVAC-13104 feat: Add cli shim package for npx qvac support Feb 10, 2026
@elchiapp elchiapp closed this Mar 4, 2026
@elchiapp elchiapp reopened this Mar 4, 2026
@opaninakuffo opaninakuffo closed this by deleting the head repository Apr 9, 2026
iancris added a commit that referenced this pull request Sep 1, 2026
…297 @ 9d181fe64)

*** DO NOT MERGE THIS COMMIT — REVERT IT BEFORE THIS PR LANDS. ***

The PR itself is meant to merge; only this commit is throwaway. It pins all
seven fabric consumers at an unpublished, un-tagged branch head so CI can
validate them against it. Merging it would make the repo depend on a local
overlay directory and a floating commit that no registry entry describes.

This is a SECOND, INDEPENDENT overlay generation. 314c362 already reverted
the first three (598bb0b, 8e9633d, cb96599) from the 10297.1.0 round.
That revert does NOT cover this commit — this one needs its own revert.

What it validates
-----------------
temp-10297 has moved five commits past v10297.1.0, to 9d181fe64. The diff
v10297.1.0...9d181fe64 touches eight files:

  Vulkan          ggml-vulkan.cpp, vulkan-shaders/topk_radix_select.comp (new),
                  vulkan-shaders-gen.cpp
  Qwen4-Next      src/models/qwen4exp.cpp, src/models/models.h,
                  src/llama-kv-cells.h            (upstream PR #229)
  Fused-op        src/llama-context.cpp — auto_fgdn / auto_flid default to false
  Tests           tests/test-backend-ops.cpp

No addon change accompanies this pin. src/llama-arch.cpp is NOT in that set,
so llm_arch_supports_sm_tensor is unchanged and the 27-entry denylist in
LoadFitNormalization.cpp stays correct. The llama-context.cpp change only
flips two fused-op autotune defaults; it does not touch SPLIT_MODE_TENSOR or
its flash-attention requirement.

Contents
--------
- vcpkg-overlays/ports/qvac-fabric/{portfile.cmake,vcpkg.json}, copied verbatim
  from the registry at origin/main, with exactly three edits: REF pinned to the
  literal commit instead of v${VERSION}, the matching archive SHA512, and the
  version set to 10297.1.1.
- "overlay-ports" added as the first key of the seven consumer
  vcpkg-configuration.json files.

Deliberately NOT changed: each consumer's default-registry.baseline (all seven
differ and none may move), and the "version>=" floors — 10297.1.1 already
satisfies the existing >= 10297.1.0, and raising floors is Phase B's job.

The distinctive 10297.1.1 version is what makes the pin falsifiable: an install
log must show the port resolving out of vcpkg-overlays/ and then

  Building qvac-fabric[...]@10297.1.1

A "Restored N package(s)" line alone does not prove this ref was compiled.

Rollout-Overlay: qvac-fabric 10297.1.1 ref=temp-10297 sha=9d181fe643481d9a1cdf241871fe5935ae407ebe

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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