Baixar Vayu 0.38.0 per a Windows

0.38.0 - 2026-10-01
Read Changed before updating: this version upgrades the workspace
database, and earlier versions cannot open it afterwards. The headline changes
are a Postman Collection export, path variables (:id in a URL) with their own
table, and Postman's per-request protocol settings. The Linux AppImage and
.deb start again on Ubuntu 22.04 and Debian 12.
Added
- Export to Postman. Export as Postman Collection in the Spec tab and
the collection tree menu writes a Postman v2.1 collection file. Auth secrets
and secret variables are left blank unless you choose to include them. An
imported collection exports close to how it came in: saved responses,
variable types and descriptions, header types, scripts (in order, with
disabled ones kept off), and the original auth block are written back. The
MCP server has a matching export_postman tool.
- Path variables. A :name segment in the URL gets a row in a new Path
variables table on the Params tab, and the value is sent in its place.
Values are encoded the way Postman encodes them. Postman and Insomnia path
variables import into the table, and the table carries over into code
snippets and the Postman and OpenAPI exports.
- Save as example keeps the request as it was when you clicked Send, so
the Postman export writes the request that actually produced the response.
- Postman's protocol settings, per request. The request's Settings tab
has Disable cookie jar, Send URL without encoding, and a Don't
send automatic headers list (User-Agent, Accept, Accept-Encoding,
Content-Type, the correlation id). Postman's disableCookies, disableUrlEncoding and
disabledSystemHeaders import into them and export back.
- Postman Hawk, OAuth 1, EdgeGrid and JWT auth are kept on import, so they
export back. Vayu does not sign requests with them, and the import preview
says so, including when the auth is set on a collection or folder.
Changed
- The workspace database moves to schema version 2. Once 0.38.0 opens a
workspace, earlier versions refuse it, so going back to 0.37 means restoring
a backup.
- The Linux build needs glibc 2.35 or later: Ubuntu 22.04, Linux Mint 21,
Debian 12, Fedora 36 or newer.
Fixed
- The Linux AppImage and .deb failed to start on Ubuntu 22.04, Linux Mint
21 and Debian 12 (GLIBC_2.38 not found), so the app opened without an
engine.
- A saved light or dark theme was ignored at launch and the app followed the
system theme.
- At launch, the collection tree, the Launcher and a restored request tab
could show "Couldn't reach Vayu's engine" while the engine was still
starting.
- Editing an imported request's or collection's auth left the old imported
credentials stored beside the new ones.
- An export without secrets still wrote the client secret, refresh token and
PKCE code verifier nested in an imported OAuth 2.0 block.
- Editing an imported collection variable dropped its description.
- Replaying a design run whose path value was still a {{variable}} sent
/users/:id literally, and Save to request cleared the row.
- Internal: a much faster pre-commit lint for engine test files, dependency
updates, and documentation kept in step with all of the above.