chore(deps): Bump github.com/CosmWasm/wasmvm from 1.4.0 to 1.4.1

[dependabot]

Bumps github.com/CosmWasm/wasmvm from 1.4.0 to 1.4.1.

Release notes

Sourced from github.com/CosmWasm/wasmvm's releases.

v1.4.1

Build artifacts generated at this tag.

Commits

• 41f7ccd [skip ci] Built release libraries
• f8b6b84 Retract 1.4.0 release
• b75a7ec Bump cosmwasm
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[helder-moreira]

goreleaser also must be updated to download the correct libs

[Unique-Divine]

@helder-moreira, which file needs to be updated? I see:

• contrib/make/release.mk, which depends on the version nibiru
• contrib/docker/goreleaser.Dockerfile, which just uses binaries in a container
• contrib/make/build.mk, which refers to $WASMVM_VERSION

WASMVM_VERSION := $(shell go list -m github.com/CosmWasm/wasmvm | awk '{sub(/^v/, "", $$2); print $$2}')

Where do we make the external lib changes?

[helder-moreira]

@helder-moreira, which file needs to be updated? I see:

• contrib/make/release.mk, which depends on the version nibiru

• contrib/docker/goreleaser.Dockerfile, which just uses binaries in a container

• contrib/make/build.mk, which refers to $WASMVM_VERSION

WASMVM_VERSION := $(shell go list -m github.com/CosmWasm/wasmvm | awk '{sub(/^v/, "", $$2); print $$2}')

Where do we make the external lib changes?

Should be .goreleaser.yml on project root. Both on darwin and linux builds.

[Unique-Divine]

Ah, I see. Do you think we could load that version number from the go.mod directly similar to our build script?

[helder-moreira]

Ah, I see. Do you think we could load that version number from the go.mod directly similar to our build script?

No, not in an easy way. But I can try to have a better look when possible. The problem is that you can't use env vars in pre-hooks.

[Unique-Divine]

Ah, I see. Do you think we could load that version number from the go.mod directly similar to our build script?

No, not in an easy way. But I can try to have a better look when possible. The problem is that you can't use env vars in pre-hooks.

This should work. If you load it in the pre block instead of env, I think you get the expected behavior:

• fix(.goreleaser.yml): Load version for wasmvm dynamically #1631