Repository navigation
chore: streamline build caches and development workflow - #99
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reduce build storage growth and repeated work while preserving the full release gate.
--forcerebuild../pobr cachestorage report and align developer documentation and CI comments with the current commands.Validation: 31 workflow tests, 15 WASM/data script tests, 100 data-library tests, and 3 support-gating tests passed. After clearing the project target, CLI, WASM and Web production builds passed. Repeated support tests took 3.9s and verified WASM reuse took 2.6s. These selected targets produced 842 MiB / 1,577 files with no incremental files; the shared sccache was retained. Full branch CI passed on
1d6fa25: https://github.com/ackness/pobr/actions/runs/36713255586 (Rust lint, complete Rust tests/doctests/data checks, Web unit/Worker tests, real WASM build, E2E, and standalone-package smoke).Tradeoff: disabling incremental compilation can make recompiling changed crates slower; unchanged targets still reuse Cargo artifacts. Existing caches are not automatically deleted.