iotaledger / iotaledger/notarization
[CI] Reduce duplication across workflow jobs and actions
- Dominant language
- Rust
- Stars
- 5
- Forks
- 7
- Avg merge
- 10h 34m
- Merged PRs (30d)
- 11
Description
## Summary
The CI/CD workflows now support both notarization and audit trail packages, but this has introduced duplication that should be consolidated.
## Areas to improve
- **`shared-build-wasm.yml`** is parameterized but each consumer workflow still duplicates the full job definition (build + test) for each package — consider a matrix or reusable workflow pattern
- **`build-and-test.yml`** has near-identical `test-wasm-notarization` and `test-wasm-audit-trail` jobs that differ only in paths, artifact names, and env var setup
- **`wasm-publish.yml`** duplicates build/release job pairs per package — could use a matrix with `include` to reduce this
- **`upload-docs.yml`** duplicates S3 upload steps per package
- **`wasm-retag-npm.yml`** and `wasm-publish.yml` retag steps are copy-pasted per package
- **Move package test/publish steps** in `build-and-test.yml` follow the same pattern and could be consolidated
## Acceptance criteria
- [ ] Reduce duplicated job definitions where possible (matrix strategies, reusable workflows, or composite actions)
- [ ] Ensure no functional regression — all existing tests and publish flows continue to work
- [ ] Keep the `package` selector in publish/retag workflows
Contributor guide
Assessment
This issue has not been assessed yet.