Skip to content

fix(action): update for install script improvements and v2.0.1#13

Merged
ricochet merged 5 commits intowasmCloud:mainfrom
ericgregory:v2-update
Mar 31, 2026
Merged

fix(action): update for install script improvements and v2.0.1#13
ricochet merged 5 commits intowasmCloud:mainfrom
ericgregory:v2-update

Conversation

@ericgregory
Copy link
Copy Markdown
Contributor

@ericgregory ericgregory commented Mar 24, 2026

Updates the action to work with the improved install scripts and bumps the default wash version to v2.0.1. Depends on wasmCloud/wasmCloud#5006.

What changed

Default version: Bumped to v2.0.1.

Install step simplification: The install scripts now default to ~/.wash/bin instead of the current working directory. The action sets INSTALL_DIR directly to the tool cache path via environment variable, so the binary lands in the right place immediately. This removes the previous pattern of installing to cwd and then copying the binary into the cache:

- export WASH_VERSION="${wash_version}"
- curl -sSL https://wasmcloud.com/sh | bash -s -- -v
- mkdir -p "${wash_cache_dir}"
- cp ./wash "${wash_cache_dir}/wash"
- chmod +x "${wash_cache_dir}/wash"
+ # INSTALL_DIR and WASH_VERSION set via env:
+ curl -sSL https://wasmcloud.com/sh | bash -s -- -v

Profile patching is automatically skipped in CI ($CI=true is set by GitHub Actions), so no --no-modify-path flag is needed.

Signed-off-by: Eric Gregory <[email protected]>
Signed-off-by: Eric Gregory <[email protected]>
…l copy

The install scripts now default to ~/.wash/bin, so the action must
explicitly set INSTALL_DIR to the tool cache path. This replaces the
previous pattern of installing to cwd and then copying the binary into
the cache directory.

Signed-off-by: Eric Gregory <[email protected]>
@ericgregory ericgregory changed the title chore(docs): bump for v2.0.1 fix(action): update for install script improvements and v2.0.1 Mar 25, 2026
@ricochet ricochet merged commit 509d0e2 into wasmCloud:main Mar 31, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants