Contract deployment fails due to change in 0.0.9

[jyulin2000]

When using terrain deploy to deploy the default project (counter), compilation succeeds, but the deployment fails because it tries to use a file called counter-aarch64.wasm despite the fact that the wasm artifact produced is counter.wasm.

Log:

Finished, status of exit status: 0
cp: artifacts/counter-aarch64.wasm: No such file or directory
    Error: Command failed: cp artifacts/counter{-aarch64,}.wasm
    cp: artifacts/counter-aarch64.wasm: No such file or directory

terrain version from above is @iboss/terrain/0.0.9 darwin-x64 node-v17.6.0, running on macOS Big Sur Version 11.1

Traced this to line 50 in the most recent commit to src/lib/deployment.ts, seems like an error with the string literal producing the filename.

I fixed this temporarily for myself by reverting to 0.0.8, but this looks like a simple bug.

[p0mvn]

Experiencing a similar problem on @iboss/terrain/0.0.9 linux-x64 node-v16.14.2

Switching to 0.0.8 also resolved this

[ethanlolomg]

Experiencing a similar problem on @iboss/terrain/0.0.9 linux-x64 node-v16.14.2

Switching to 0.0.8 also resolved this

How did you switch your terrain version?

[p0mvn]

npm install -g @iboss/terrain@< version >

[iboss-ptk]

Noted the bug, will sort this out!