Aquesta és una versió anterior. La versió actual és la 0.47.0. Vayu 0.47.0 · Data de publicació:
Fitxers d’instal·lació 0.29.1
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE (NSIS) · en-US | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
0.29.1 - 2026-09-13
A round of import fixes across every supported format, found by testing the importer against real-world OpenAPI, Postman, Insomnia and JMeter files and auditing it field by field against each format's own specification.
Fixed
- A disabled element in a JMeter plan now stays disabled on import. A sampler, controller or assertion turned off in JMeter's own UI used to import as active anyway, with no way to turn it back off.
- Insomnia path parameters now resolve correctly. A URL using Insomnia's :name path-parameter syntax used to import with the literal :name still in it, so the request failed on first send.
- An explicit "No Auth" on an Insomnia request no longer inherits its folder's credentials. A request set to send no authentication, under a folder that requires it, was sending the folder's credentials anyway.
- An OpenAPI API key declared in a cookie is no longer silently sent as a header. The request now imports with no auth set, rather than a credential going somewhere the API never asked for it.
- A JMeter sampler's Follow Redirects / Redirect Automatically setting is now carried over on import.
- A JMeter response assertion checking the sampled URL now maps onto the request's URL rather than its body; one checking something else Vayu has no field for (request data, request headers, response message) is flagged instead of silently checked against the wrong text.
- A JMeter If/Switch/infinite-loop controller Vayu could not translate now shows up in the import summary instead of disappearing with its logic unexplained.
- An OpenAPI security scheme with no recognizable OAuth2 flow now imports with no auth set, instead of a plausible-looking but nonfunctional configuration.
- An OpenAPI OAuth2 flow's refresh-token URL is now imported.
- An OpenAPI 3.1 document whose operations are declared under webhooks no longer imports silently as zero requests.
- A Postman request body switched off in Postman is no longer sent anyway on import.
- A Postman request's client certificate or proxy override, and a JMeter file upload, are not yet imported but now show up in the import summary rather than vanishing without a trace.
- Smaller OpenAPI fixes: a parameter described only through its content type now keeps its example value, a 3.1 tuple-shaped array schema samples each position instead of coming back empty, and a deprecated operation is flagged in the import summary.
