Skip to content

Fix Windows source-contract self-match (4.4.0) - #4

Merged
cursor[bot] merged 2 commits into
mainfrom
cursor/windows-source-contract-5371
Aug 18, 2026
Merged

Fix Windows source-contract self-match (4.4.0)#4
cursor[bot] merged 2 commits into
mainfrom
cursor/windows-source-contract-5371

Conversation

@devlifeX

@devlifeX devlifeX commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Problem

v4.3.0 failed Windows CI (cargo test --workspace) on:

tests::packaged_connect_stages_into_the_helper_generation_root

The source contract used include_str!("lib.rs") plus !contains of the old user_data_dir.join("runtime").join("generations") snippet. That needle is also the assertion itself, so the test always failed. #![cfg(windows)] hid it from Linux.

Fix

  • Scan only the production half before mod tests {.
  • Split the forbidden needle so a whole-file include cannot match the assertion.
  • Mirror the same check in scripts/tauri-contract.test.mjs so Linux pnpm check covers it.
  • Record the lesson; note it on ADR 0064.
  • Bump to 4.4.0 and tag v4.4.0 so GitHub Release publishes (4.3.0 is already tagged).

Runtime Connect/staging behavior is unchanged from 4.3.0. The Windows cargo test --workspace job on this branch already passed.

Open in Web Open in Cursor 

include_str!("lib.rs") matched the forbidden-path assertion itself, so
windows-2025 cargo test failed after 4.3.0. Scan the production half,
split the needle, and cover the same check in the Linux script contract.

Co-authored-by: Dariush vesal <dariush.vesal@gmail.com>
@devlifeX
devlifeX marked this pull request as ready for review August 18, 2026 16:57
Keeps the source-contract fix that unblocked windows-2025 cargo test.

Co-authored-by: Dariush vesal <dariush.vesal@gmail.com>
@cursor cursor Bot changed the title Fix Windows source-contract self-match (4.3.1) Fix Windows source-contract self-match (4.4.0) Aug 18, 2026
@cursor
cursor Bot merged commit 82cb04f into main Aug 18, 2026
5 checks passed
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