release: v0.2.6: Stable type-aware linting and more reliable task caching - #2217
Merged
wan9chi merged 4 commits intoJul 23, 2026
Merged
release: v0.2.6: Stable type-aware linting and more reliable task caching#2217wan9chi merged 4 commits into
wan9chi merged 4 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
✅ Deploy Preview for viteplus-preview canceled.
|
Sorry, something went wrong.
NAPI bakes the package.json version into binding/index.cjs version checks. The prepare_release workflow bumps package.json but does not regenerate this file, so the CI build's regeneration step produces a diff that the post-build no-unexpected-changes guard rejects.
Copy link
Copy Markdown
Contributor
Native binary sizes (7c27a20)Final release artifacts built by the canonical build-upstream and build-windows-cli actions.
|
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Registry bridge build (5793943)This commit build is published to the registry bridge, which serves these as ordinary npm versions (every other package proxies to npmjs):
Install the Vite+ CLI built from this commit, then migrate a project: # macOS / Linux
curl -fsSL https://vite.plus | VP_PR_VERSION=2217 bash# Windows (PowerShell)
$env:VP_PR_VERSION="2217"; irm https://vite.plus/ps1 | iexAfter installing, upgrade the current project's vite-plus to this test build with: vp migrateOr point your package manager at the bridge registry https://registry-bridge.viteplus.dev/:
Then pin the build (vite aliases to vite-plus-core; pnpm can use a catalog, npm an overrides entry): {
"devDependencies": {
"vite-plus": "0.0.0-commit.57939439ddcb16d9f54ebf7d41432893182ee46d",
"vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.57939439ddcb16d9f54ebf7d41432893182ee46d"
}
} |
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
🐳 Docker preview imageBuilt from this PR's registry bridge build:
# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-2217 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-2217Quick check: docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-2217 vp --versionSee docs/guide/docker.md for usage. |
Sorry, something went wrong.
This was referenced Jul 22, 2026
Copy link
Copy Markdown
Collaborator
@wan9chi 🙇 I forgot to update PR title so this might be outdated. |
Sorry, something went wrong.
Copy link
Copy Markdown
Member
|
@liangmiQwQ Updated the release notes to match the final implementation: vp build removes the redundant Vite startup banner rather than rebranding it. Thanks for catching this. |
Sorry, something went wrong.
wan9chi
added a commit
that referenced
this pull request
Jul 23, 2026
## Summary - disable pnpm and Yarn package-age gates in the create approval-flow fixtures - regenerate snapshots around stable build-script approval behavior - avoid wall-clock failures when pinned upstream dependencies mature Fixes the cross-platform snapshot failures blocking #2217. ## Motivation While preparing v0.2.6 in #2217, the three `create_approve_builds` snapshots failed on Linux, macOS, and Windows. The release branch inherited the dependency upgrade from #2214, including OXC 0.141.0. When #2214 recorded these snapshots, the OXC packages were still inside the package-manager age window. The pnpm snapshots therefore included temporary `minimumReleaseAgeExclude` entries. The Yarn fixture stopped at an OXC quarantine error before it reached the `core-js` build-approval behavior that the fixture was meant to test. By the time release CI ran, the same OXC packages were old enough to install normally. No Vite+ behavior had changed, but pnpm no longer generated the temporary exclusions and Yarn completed installation. The resulting output was correct, but it no longer matched snapshots captured under the earlier registry state. Simply accepting the new snapshots would leave the fixtures dependent on package publication time. A future dependency upgrade could make them fail again while the new package is inside the age window. These fixtures should only test whether `vp create` detects, reports, and approves blocked build scripts. Disabling age gates in the three fixture environments makes that behavior deterministic without changing Vite+ or package-manager defaults for users. The regenerated snapshots now cover pnpm `allowBuilds`, Yarn `dependenciesMeta.built`, and the guidance shown when a build remains unapproved. ## Validation - `pnpm build` - `UPDATE_SNAPSHOTS=1 just snapshot-test create_approve_builds` - `just snapshot-test create_approve_builds`
wan9chi
approved these changes
Jul 23, 2026
wan9chi
left a comment
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
Release version bump and notes validated by the release trigger.
Sorry, something went wrong.
Copy link
Copy Markdown
Member
|
Discord announcement draft: :viteplus: **vite-plus v0.2.6 is out** :tada:
Stable type-aware linting and more reliable task caching.
**Highlights**
:sparkles: Bundled type-aware linting now uses stable tsgolint 7.
:zap: `vp run` caches larger input sets, handles npm workspace patterns starting with `./`, and shows more accurate error messages.
:sparkles: `vp build` no longer repeats the Vite startup banner.
**Upstream Upgrades**
:package: Vite `8.1.4` -> `8.1.5`, Rolldown `1.1.5` -> `1.2.0`
:package: tsdown `0.22.7` -> `0.22.13`, Oxlint `1.73.0` -> `1.75.0`
:package: oxlint-tsgolint `0.24.0` -> `7.0.2001`, Oxfmt `0.58.0` -> `0.60.0`
**Also in this release**
- Fixed documentation anchors and easier access to Migration Rules
**Bundled versions**
vite `8.1.5`, rolldown `1.2.0`, tsdown `0.22.13`, vitest `4.1.10`, oxlint `1.75.0`, oxlint-tsgolint `7.0.2001`, oxfmt `0.60.0`
**Upgrade**: `vp upgrade`
Full notes: <https://github.com/voidzero-dev/vite-plus/releases/tag/v0.2.6>
Thanks to new contributor [@charpeni](https://github.com/charpeni) :wave: |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release vite-plus v0.2.6: Stable type-aware linting and more reliable task caching.
This release moves Vite+'s type-aware linting to the stable tsgolint 7 engine, updates the bundled build and formatting tools, strengthens vp run caching and workspace discovery, and removes the redundant vp build startup banner.
Highlights
Refactor
Docs
Chore
Bundled Versions
Upgrade
New Contributors
Welcome @charpeni.
Full Changelog: v0.2.5...v0.2.6
Merging this PR will trigger the release workflow.