[fi3ework]

Bump every package to 0.4.3 (pnpm bump --release patch).

v0.4.2..main has no breaking changes:

• feat(vscode): add rstack.rstackCli.packagePath setting (feat(vscode): add rstack.rstackCli.packagePath setting #104)
• fix(vscode): filter selected Rstest cases in projects (fix(vscode): filter selected Rstest cases in projects #108)
• chore(deps): update dependency ovsx to ^1.3.0 (chore(deps): update dependency ovsx to ^1.3.0 #105)
• chore(deps): update node.js to v26.12.1 (chore(deps): update node.js to v26.12.1 #106)
• chore(deps): update rstack toolchain (chore(deps): update rstack toolchain #107)
• chore(deps): update dependency yuku-parser to ^0.19.0 (chore(deps): update dependency yuku-parser to ^0.19.0 #98)
• test(vscode): raise lint E2E mocha default timeout (test(vscode): raise lint E2E mocha default timeout #102)
• chore(deps): update rstack toolchain (chore(deps): update rstack toolchain #101)
• chore(deps): update node.js to v26.11.1 (chore(deps): update node.js to v26.11.1 #99)
• chore(deps): update dependency rstack to v0.8.3 (chore(deps): update dependency rstack to v0.8.3 #97)

After merge: run the Release workflow from main (see CONTRIBUTING.md → Releasing).

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-22T07:20:05.396953Z	ab21ac6	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.