CI/Release Workflows: Fix validation bypass and wasm-tools version mismatch

Abierto
#965 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
56/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust, wasm

Línea de trabajo

Read .github/workflows/publish.yml and .github/actions/install-tools/action.yml to compare the wasm-tools versions. Then inspect the CI workflow's dorny/paths-filter conditions and .github/scripts/validate-proposals.js, which reads docs/ComponentModelFeatures.md. Done means the tool versions are consistent and validation runs for changes to the scripts or feature document; the issue does not name tests to run.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

wasm-tools Version Mismatch (publish.yml vs install-tools/action.yml)
Issue: There is a discrepancy in the wasm-tools version used across different jobs, which can break tooling dependent on newer Component Model features (like cm-map and cm-implements introduced in WASI 0.3.1).
Cause: The upload-wit-tarball job inside .github/workflows/publish.yml installs [email protected]. Meanwhile, .github/actions/install-tools/action.yml installs [email protected].
Impact: Version 1.214.0 is outdated and lacks support for recent Component Model features. This mismatch risks publishing failures or improper validation.

Issue: The CI workflow silently skips validation when changes are made to .github/scripts/** or docs/ComponentModelFeatures.md.
Cause: The workflow is correctly configured to trigger on changes to .github/scripts/** and .github/workflows/ci.yml. However, the dorny/paths-filter step only matches proposals/*/wit/**. Because the "Install tools" and "Validate changed proposals" steps are conditionally bound to if: steps.changes.outputs.wit == 'true', a PR that only modifies the validation scripts or the ComponentModelFeatures.md file (which is read by validate-proposals.js to check GATE_FEATURES) will never actually run the validation.

Lenguaje dominante
Rust
Estrellas
5.8k
Forks
339
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de WebAssembly/WASI

Todos los issues de WebAssembly/WASI

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.