Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: voidzero-dev/setup-vp
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.13.0
Choose a base ref
...
head repository: voidzero-dev/setup-vp
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.14.0
Choose a head ref
  • 3 commits
  • 16 files changed
  • 1 contributor

Commits on Jul 1, 2026

  1. docs: document the version release process (#101) 

    Adds a `### Releasing` subsection under `## Development` in the README,
capturing the current release process:

- Releases are published as git tags only; there is no npm package, so
`package.json` stays at `1.0.0`.
- Consumers reference the moving major tag `@v1` (or pin a SHA), so each
release moves `v1` forward.
- Steps: sync `main` and confirm `dist/index.mjs` is in sync, create the
annotated `v1.x.0` version tag (minor bump), move the `v1` major tag to
the same commit, then push the new tag and force-push `v1`.

Documents the process just used to cut `v1.13.0`.
    @fengmk2
    fengmk2 authored Jul 1, 2026
    Configuration menu
    Copy the full SHA
    a9a1f8d View commit details
    Browse the repository at this point in the history

  2. ci: auto-rebuild action bundle on Renovate dependency bumps (#103) 

    Renovate bumps to bundled deps (\`@actions/*\`, \`yaml\`, \`zod\`) or to
the \`vite-plus\` bundler change \`dist/index.mjs\`, which fails the
"Verify dist is up to date" check until someone manually runs \`vp run
build\` and commits.

This adapts the label-triggered rebuild approach from
voidzero-dev/pkg-pr-registry-bridge#47:

- New \`.github/workflows/rebuild-bundle.yml\`: on the
\`needs-bundle-rebuild\` label (same-repo PRs only), rebuild \`dist/\`
and push it back to the PR branch. Uses a GitHub App token so the push
re-triggers the PR's required checks.
- \`.github/renovate.json\`: attach the \`needs-bundle-rebuild\` label
to runtime \`dependencies\` and to \`vite-plus\`, the bumps that can
change the bundle.

Relies on the org secrets \`APP_ID\` / \`APP_PRIVATE_KEY\` (same
App/secrets as the reference repo).
    @fengmk2
    fengmk2 authored Jul 1, 2026
    Configuration menu
    Copy the full SHA
    a5a1bc2 View commit details
    Browse the repository at this point in the history

  3. feat: resolve Vite+ version from package.json / catalog / lockfile (#102 

    )

Resolve the Vite+ version from the checked-out project so CI keeps a single source of truth. Adds a `version-file` input and, when neither `version` nor `version-file` is set, auto-detects from the project's package.json (exact pin or `catalog:` across pnpm/yarn/bun), resolving a semver range through the lockfile, and falling back to `latest`. Also hardens catalog/lockfile resolution for monorepos and fixes the `vp --version` output parsing.

Closes #82
    @fengmk2
    fengmk2 authored Jul 1, 2026
    Configuration menu
    Copy the full SHA
    13e7afb View commit details
    Browse the repository at this point in the history
Loading