fix vp release tagging and verification

Author: ubugeeei

Cargo.lock

@@ -258,7 +258,7 @@ rolldown_plugin_asset_module = { path = "./rolldown/crates/rolldown_plugin_asset
 rolldown_plugin_bundle_analyzer = { path = "./rolldown/crates/rolldown_plugin_bundle_analyzer" }
 rolldown_plugin_chunk_import_map = { path = "./rolldown/crates/rolldown_plugin_chunk_import_map" }
 rolldown_plugin_copy_module = { path = "./rolldown/crates/rolldown_plugin_copy_module" }
-rolldown_plugin_data_url = { path = "./rolldown/crates/rolldown_plugin_data_url" }
+rolldown_plugin_data_uri = { path = "./rolldown/crates/rolldown_plugin_data_uri" }
 rolldown_plugin_esm_external_require = { path = "./rolldown/crates/rolldown_plugin_esm_external_require" }
 rolldown_plugin_hmr = { path = "./rolldown/crates/rolldown_plugin_hmr" }
 rolldown_plugin_isolated_declaration = { path = "./rolldown/crates/rolldown_plugin_isolated_declaration" }
@@ -285,6 +285,7 @@ rolldown_plugin_vite_reporter = { path = "./rolldown/crates/rolldown_plugin_vite
 rolldown_plugin_vite_resolve = { path = "./rolldown/crates/rolldown_plugin_vite_resolve" }
 rolldown_plugin_vite_transform = { path = "./rolldown/crates/rolldown_plugin_vite_transform" }
 rolldown_plugin_vite_wasm_fallback = { path = "./rolldown/crates/rolldown_plugin_vite_wasm_fallback" }
+rolldown_plugin_vite_wasm_helper = { path = "./rolldown/crates/rolldown_plugin_vite_wasm_helper" }
 rolldown_plugin_vite_web_worker_post = { path = "./rolldown/crates/rolldown_plugin_vite_web_worker_post" }
 rolldown_resolver = { path = "./rolldown/crates/rolldown_resolver" }
 rolldown_sourcemap = { path = "./rolldown/crates/rolldown_sourcemap" }

Cargo.toml

@@ -27,7 +27,7 @@ Vite+ is fully open-source under the MIT license.
 
 `vp release` detects likely checks from `build`, `pack`, `prepack`, `prepublishOnly`, `prepare`, and `vitePlus.release.checkScripts`. Real releases run those checks before publishing unless you pass `--no-run-checks`; dry-runs stay lightweight by default and can opt in with `--run-checks`. `--dry-run` also runs the native publisher in dry-run mode from a temporary release manifest state when the git worktree is clean. Use `--yes` for CI or other non-interactive runs, and `--version <x.y.z>` when retrying a partial publish at an exact version.
 
-Real releases always create git tags after a successful publish. Preview-only flags such as `--skip-publish` and `--no-git-tag` are therefore limited to `--dry-run`.
+Real releases always create git tags after a successful publish. When every released package shares the same target version, `vp release` also creates a repository-level `v<version>` tag so GitHub Releases and repo-wide release notes can follow the same watermark. Preview-only flags such as `--skip-publish` and `--no-git-tag` are therefore limited to `--dry-run`.
 
 ## Getting Started
 

README.md

@@ -161,7 +161,7 @@ macro_rules! first_publish_checklist {
                         "`contents: write` and `id-token: write`",
                     ),
                     text!(
-                        "Push the generated release tags back to origin so the release watermark survives CI.",
+                        "Push the generated release commit and tags back to origin so the release watermark survives CI.",
                     ),
                 ],
             ),
@@ -901,7 +901,12 @@ mod tests {
         assert!(created.contains("git config user.name \"github-actions[bot]\""));
         assert!(created.contains("vp release --first-release --yes"));
         assert!(created.contains("vp release --yes"));
-        assert!(created.contains("run: git push origin --tags"));
+        assert!(created.contains("git push origin HEAD"));
+        assert!(created.contains("git push origin --tags"));
+        assert!(
+            created
+                .contains("gh release create \"$repo_tag\" --generate-notes --title \"$repo_tag\"")
+        );
         assert!(!created.contains(PACKAGE_MANAGER_SETUP_TOKEN));
         assert!(!created.contains(INSTALL_COMMAND_TOKEN));
     }