🙋 Feature Request
The current GitHub Actions workflow (Release packages to GitHub releases) efficiently handles package publishing, but lacks robust caching for Cargo components and pre-build structure validation.
🤔 Expected Behavior
The pipeline should utilize dedicated caching for Cargo (~/.cargo and target directories) alongside npm cache to speed up compilation, and include pre-build validation checks to catch configuration or manifest errors early.
😯 Current Behavior
Currently, only npm modules are cached, and full compilation runs without an initial defensive structure check, meaning workspace or policy errors are only caught deep inside the build process.
💁 Possible Solution
Add a dedicated actions/cache step for Cargo dependencies.
Introduce a lightweight pre-build validation script before running npm run build.
🔦 Context
💻 Examples
🙋 Feature Request
The current GitHub Actions workflow (Release packages to GitHub releases) efficiently handles package publishing, but lacks robust caching for Cargo components and pre-build structure validation.
🤔 Expected Behavior
The pipeline should utilize dedicated caching for Cargo (~/.cargo and target directories) alongside npm cache to speed up compilation, and include pre-build validation checks to catch configuration or manifest errors early.
😯 Current Behavior
Currently, only npm modules are cached, and full compilation runs without an initial defensive structure check, meaning workspace or policy errors are only caught deep inside the build process.
💁 Possible Solution
Add a dedicated actions/cache step for Cargo dependencies.
Introduce a lightweight pre-build validation script before running npm run build.
🔦 Context
💻 Examples