CI/CD: Enforce or verify optimizer wasm parity for releases #66

New issue

Closed

opened 2026-04-09 03:23:43 +00:00 by PlasticDigits · 3 comments

PlasticDigits commented

2026-04-09 03:23:43 +00:00

(Migrated from gitlab.com)

Type

missing-implementation (functional)

Evidence

Makefile build-optimized vs .github/workflows/test.yml (cargo wasm only)
RELEASE_READINESS_MATRIX.md

Rationale

Production uses cosmwasm optimizer; CI must not silently diverge.

Dependencies

None.

Acceptance criteria

CI runs optimizer (cached) or verifies release artifact checksums
Deployment docs state canonical wasm policy

Epic

#57

## Type **missing-implementation** (functional) ## Evidence - `Makefile` `build-optimized` vs `.github/workflows/test.yml` (cargo wasm only) - `RELEASE_READINESS_MATRIX.md` ## Rationale Production uses cosmwasm optimizer; CI must not silently diverge. ## Dependencies None. ## Acceptance criteria - [ ] CI runs optimizer (cached) or verifies release artifact checksums - [ ] Deployment docs state canonical wasm policy ## Epic #57

PlasticDigits commented

2026-04-09 03:23:44 +00:00

(Migrated from gitlab.com)

marked this issue as related to #57

PlasticDigits commented

2026-04-13 04:10:39 +00:00

(Migrated from gitlab.com)

Implemented hybrid wasm policy: PR CI still uses fast cargo wasm in test.yml; release-grade artifacts are produced by the new contracts-wasm-optimizer.yml workflow (runs smartcontracts/scripts/optimize.sh, uploads optimized wasm + wasm-checksums.txt). Deployment guide and Makefile document that production uploads must use workspace-optimizer output, not PR wasm alone. @brouie Please verify the workflow runs successfully from Actions (workflow_dispatch) and that artifact checksums match your release process.

Implemented hybrid wasm policy: PR CI still uses fast cargo wasm in test.yml; release-grade artifacts are produced by the new `contracts-wasm-optimizer.yml` workflow (runs `smartcontracts/scripts/optimize.sh`, uploads optimized wasm + `wasm-checksums.txt`). Deployment guide and Makefile document that production uploads must use workspace-optimizer output, not PR wasm alone. @brouie Please verify the workflow runs successfully from Actions (workflow_dispatch) and that artifact checksums match your release process.

Brouie commented

2026-04-20 05:48:40 +00:00

(Migrated from gitlab.com)

@PlasticDigits Verified implementation on current main. Acceptance criteria:

CI runs optimizer: .github/workflows/contracts-wasm-optimizer.yml present. Triggers: workflow_dispatch, push to main on smartcontracts/, and tags v*. Runs smartcontracts/scripts/optimize.sh (exists + executable), emits SHA256 checksums via sha256sum cl8y_dex_*.wasm, uploads cl8y-dex-optimized-wasm artifact with wasm + wasm-checksums.txt.
Deployment docs state canonical wasm policy: deployment-guide.md explicitly states workspace-optimizer is canonical; launch-checklist.md includes wasm policy line item; wasm-admin-migration.md reinforces 'Do not upload ad-hoc cargo wasm from PR builds to mainnet'; qa-onboarding.md and local-development.md consistent. Makefile comments (lines 80-90) document the hybrid CI policy and explicitly flag cargo-only wasm as NOT a substitute for optimizer.

Hybrid CI policy (PR uses cargo wasm for speed, release uses workspace-optimizer) is clearly documented across all surfaces. Closing.

@PlasticDigits Verified implementation on current main. Acceptance criteria: - [x] CI runs optimizer: .github/workflows/contracts-wasm-optimizer.yml present. Triggers: workflow_dispatch, push to main on smartcontracts/, and tags v*. Runs smartcontracts/scripts/optimize.sh (exists + executable), emits SHA256 checksums via sha256sum cl8y_dex_*.wasm, uploads cl8y-dex-optimized-wasm artifact with wasm + wasm-checksums.txt. - [x] Deployment docs state canonical wasm policy: deployment-guide.md explicitly states workspace-optimizer is canonical; launch-checklist.md includes wasm policy line item; wasm-admin-migration.md reinforces 'Do not upload ad-hoc cargo wasm from PR builds to mainnet'; qa-onboarding.md and local-development.md consistent. Makefile comments (lines 80-90) document the hybrid CI policy and explicitly flag cargo-only wasm as NOT a substitute for optimizer. Hybrid CI policy (PR uses cargo wasm for speed, release uses workspace-optimizer) is clearly documented across all surfaces. Closing.

Brouie (Migrated from gitlab.com) closed this issue

2026-04-20 05:48:43 +00:00