Description

tauri-plugin-wdio-webdriver has never shipped permissions/autogenerated/reference.md (1.0.0 through 1.5.0). Its build.rs runs tauri_plugin::Builder, which writes that file at build time unless it already holds the exact bytes it would generate. In a read-only vendored source tree (cargo vendor + chmod -R a-w), the write fails with unable to create permissions dir: Permission denied.

Cause: the root .gitignore has **/autogenerated/**/*. The webdriver crate has no include =, so cargo package respects .gitignore and leaves the generated files out. tauri-plugin-wdio only ships them by luck: its include = [...] makes cargo read the filesystem, so it picks up whatever the pre-publish build generated.

Fix

This takes the same approach as Tauri's official plugins (tauri-plugin-shell, tauri-plugin-fs): commit the generated files and make sure they ship byte-for-byte.

• Commit the generated permission files for both crates. A new .gitignore rule, !packages/tauri-plugin*/permissions/autogenerated/**, re-includes everything under that directory. Any new generator output therefore shows up in the drift checks and the package file list. The files were generated with cargo check, so they're exactly what tauri_plugin::Builder writes with the locked tauri-plugin / tauri-utils.
  • webdriver crate: reference.md only, since its command list is empty.
  • tauri-plugin: reference.md plus commands/*.toml.
  • permissions/schemas/schema.json doesn't change for either crate.
• Keep the files exact through release, Windows and old Tauri:
  • turbo.json: @wdio/tauri-plugin#build:rust no longer lists permissions/autogenerated/** and permissions/schemas/** as outputs. The release workflow runs this task, and a cache hit would otherwise restore stale bytes over the committed files before publishing. Its inputs never included permissions/default.toml or Cargo.lock. No other task or scripts/test-package.ts relies on these as build outputs; test-package.ts copies the plugin source tree.
  • tauri-plugin-wdio: the tauri-plugin build-dependency floor goes from 2.0.0 to 2.5.3, matching the webdriver crate. With the old floor, apps on older Tauri could resolve a tauri-utils whose generator writes a different reference.md, so read-only builds would still fail.
  • tauri-plugin-wdio: the unused runtime tauri-plugin dependency and the unused tauri-build build-dependency are removed. The crate's Cargo.lock and both Tauri fixture lockfiles drop the tauri-build edge. The crate's lockfile also updates its own version entry to 1.5.0, which matches main.
  • .editorconfig: insert_final_newline = false now applies only to permissions/schemas/**. The schemas have no final newline, but the autogenerated files end with one, and an editor stripping it would break byte identity. Biome's matching ignore comment is corrected.
• CI, in _ci-rust-clippy.reusable.yml behind a new generated-permissions-crates input. Only the Linux Tauri clippy job enables it, because the generated files don't depend on the platform. The step runs even if clippy failed. For each crate, it:
  1. deletes permissions/autogenerated, runs cargo check, and fails if git status -- <crate>/permissions isn't clean. This keeps the committed files in sync with build.rs; deleting first means the check can't pass just because the build script didn't re-run. The error tells you to do the same locally: delete permissions/autogenerated, rebuild, and commit the result, including deletions.
  2. fails if there are no committed files under permissions/autogenerated, or if cargo package --list is missing any committed file under permissions/autogenerated. It lists the missing files.
• Nightly crate-drift.yml re-resolves dependencies and runs cargo check. It now deletes permissions/autogenerated first, the same as the PR check. The run then fails if the build changed its committed permissions/ files, so a new tauri-utils release that changes the generator's output gets caught. The auto-filed issue's text covers both cases.
• scripts/detect-changes.ts no longer classes *.md under packages/<pkg>/permissions/** as docs, so a PR that only touches a generated reference.md still runs the Tauri jobs.

Why there's no read-only vendored build in CI: a dependency's build script makes no writes when two things hold: the committed files match what the generator produces, and they're in the package. The checks above cover exactly those. A CI read-only build would need cargo package, unpacking the crate, a copied lockfile and a throwaway consumer crate. The only extra case it would catch is a future Tauri build script writing outside permissions/. I ran that build once by hand instead (see Testing).

The crate versions in Cargo.toml are unchanged; releasekit handles them. rust-version is also unchanged, so MSRV-aware resolvers still pick this release for apps on older toolchains.

Related Issues

Closes #730

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 📖 Documentation update
• 🎨 Code style/refactoring (no functional changes)
• 🔧 Internal/tooling change (build scripts, CI, etc.)
• ⚡ Performance improvement

Scope

• scope:electron - Electron service and CDP bridge
• scope:tauri - Tauri service and plugin

Checklist

• I have read the CONTRIBUTING guidelines
• I have added tests that prove my fix is effective or that my feature works
• All new and existing tests pass (pnpm test)

The tests are the new CI checks plus new detect-changes cases. I didn't run the full pnpm test locally. I did run pnpm test:scripts, cargo test for both crates, and the pre-push hook's turbo typecheck/test, and all of them pass.

Testing

Run locally on macOS (arm64), rustc 1.97.1:

• Packaging: cargo package --list now includes every committed file under permissions/autogenerated and permissions/schemas for both crates. With the old .gitignore and the files untracked, the webdriver crate's list didn't include reference.md, even though the file was on disk.

• Read-only vendored build, run by hand: cargo package --no-verify on the webdriver crate, unpack the .crate, chmod -R a-w, then cargo check --offline a consumer crate that depends on it by path. It passes. With permissions/autogenerated removed from the unpacked crate, it fails with the error from the issue (unable to create permissions dir: ... PermissionDenied).

• New CI step script, extracted from the workflow and run per crate:

  • It passes for both crates with the final manifests; the generated files come out byte-identical to the committed ones.
  • It fails as intended when a command is temporarily added to tauri-plugin's build.rs. It reports the new untracked commands/drift_probe.toml and the modified reference.md and schema.json, and the error gives the delete, rebuild and commit advice.
  • It fails and lists the missing files when they're left out of the package:
    • tauri-plugin with its include narrowed: missing commands/*.toml (all six are listed).
    • webdriver crate with an exclude: missing reference.md.

• New crate-drift.yml block (delete, cargo check, git status), run under /bin/bash 3.2 to match the macOS runner:

  • It passes for the webdriver crate and for dioxus-bridge, which has no permissions/ directory.
  • Without the rebuild, it fails when a committed permission file is modified.

• .gitignore: a new file anywhere under permissions/autogenerated/, including in a new subdirectory, shows up as untracked.

• .editorconfig: the committed files contain no CR bytes or trailing whitespace. Only the two schema.json files lack a final newline.

• Removed dependencies: nothing in tauri-plugin's src/ or build.rs uses tauri_plugin at runtime or tauri_build. In the fixture lockfiles, the only other change cargo would make is moving the two path crates' stale self-versions to 1.5.0, which main already has.

• detect-changes: the new spec cases fail against the old classifier and pass with the change. pnpm test:scripts passes (111 tests), and typecheck:scripts is clean.

• Lint and Rust: cargo clippy --all-targets -- -D warnings and cargo test are clean for both crates (webdriver: 28 tests pass; tauri-plugin has no Rust tests). actionlint is clean on all changed workflows. Biome is clean on the changed TS/JSON.

• Left to CI: the new step on ubuntu-latest in Clippy Tauri Crates [Linux]. crate-drift.yml also runs on this PR because the workflow file changed, so its Fresh deps legs run against today's newest dependencies.

• Unit tests added/updated

• Integration tests added/updated

• E2E tests added/updated (if applicable)

• Manually tested on: macOS 26 (arm64)

Additional Context

The committed files are tied to the generator in the locked tauri-plugin / tauri-utils. If a later bump changes the output, the clippy-job check fails on the PR and the nightly crate-drift check fails on main. In both cases, the fix is to delete permissions/autogenerated, build the crate and commit the regenerated files. Building a Tauri fixture app against a newer Tauri would also rewrite them in the working tree.

🤖 Generated with Claude Code