postinstall not working

[jcalfee]

What is the proper way to put the correct binaries in the path after install?

If post install would work for me, this would be ideal because I have a path for development and only if I install this do I want to put the binaries in the root folder (mise automatically includes the root folder in the path).

[hooks]
postinstall = "mv -v nebula-ca/build/{{os()}}-{{arch(x64='amd64', arm64='arm64')}}/* ."

There's just no output other than a faulty warning (I do have double parenthesis in the packages file):

mise install http:my-script

mise WARN deprecated [legacy-version-template]: Use {{ version }} instead of {version} in URL templates This will be removed in mise 2027.3.0.
http:my-script@1.0.0 generate checksum my-script-1.0.0-linux-x64.tar.gz ✔

I do not see a mv -v anywhere in the trace. it likely is not running. Do I even have this thing in the right file? Why is there no error? I see other types of errors. It seems to have some sort of schema validation in VSCodium; so the file format appears to be okay to me.

MISE_TRACE=1 mise install http:my-script

[env]
TOOL_NAME = "my-script"
VERSION = "1.0.0"
_.path = { path = ["nebula-ca/build/{{os()}}-{{arch(x64='amd64', arm64='arm64')}}"], tools = true } # for development only

[tasks.build-nebula-x64]
dir = "nebula-ca"
run = "make build/linux-amd64/nebula build/linux-amd64/nebula-cert"
outputs = ["nebula-ca/build/linux-arm64/nebula", "nebula-ca/build/linux-arm64/nebula-cert"]

[tasks.build-nebula-arm64]
dir = "nebula-ca"
run = "make build/linux-arm64/nebula build/linux-arm64/nebula-cert"
outputs = ["nebula-ca/build/linux-arm64/nebula", "nebula-ca/build/linux-arm64/nebula-cert"]

[tasks.package-x64]
depends = ["build-dns-x64", "build-nebula-x64"]
env = { PLATFORMS = "linux-x64" }
sources = [
  "my-script",
  "nebula-ca/build/linux-amd64/nebula",
  "nebula-ca/build/linux-amd64/nebula-cert",
  "mise.toml"
]

[tasks.package-arm64]
depends = ["build-dns-arm64", "build-nebula-arm64"]
env = { PLATFORMS = "linux-arm64" }
sources = [
  "my-script",
  "nebula-ca/build/linux-arm64/nebula",
  "nebula-ca/build/linux-arm64/nebula-cert",
  "mise.toml"
]

[hooks]
postinstall = "mv -v nebula-ca/build/{{os()}}-{{arch(x64='amd64', arm64='arm64')}}/* ."

[tasks.publish]
depends = ["package-x64", "package-arm64"]
# ...

[jdx]

Two things going on here:

1. The [hooks] section is experimental and silently no-ops unless you enable it:

[settings]
experimental = true

Also, the preinstall/postinstall hook only runs when your current working directory is under the config file's project root.

2. You likely want the tool-level postinstall option, not the [hooks] block.

The tool-level postinstall runs immediately after that specific tool is installed, which matches what you're describing. It's not experimental, and it gets MISE_TOOL_INSTALL_PATH, MISE_TOOL_NAME, and MISE_TOOL_VERSION env vars:

[tools]
"http:my-script" = { version = "1.0.0", url = "...", postinstall = "mv -v nebula-ca/build/{{os()}}-{{arch(x64='amd64', arm64='arm64')}}/* ." }

See tool-level postinstall docs.

3. The deprecation warning is unrelated — somewhere in your tool config you have a URL template using {version} (single braces). Change it to {{ version }} (double braces with spaces). That warning isn't blocking the hook.

This comment was generated by an AI coding assistant.

[jcalfee]

Thanks, but your answer still has several mysteries (several problems).

• why is version hard coded?
• why do I need a URL, this has nothing to do with a URL.

Using version = "{{MISE_TOOL_VERSION}}" did not work: "mise ERROR Variable MISE_TOOL_VERSION not found in context while rendering '__tera_one_off'"

Omitting url: mise ERROR Failed to install http:my-script@1.0.0: Http backend requires 'url' option

The URL is in a different file. It's in the a shared mise.toml configuration file with all the other packages. It's not in this file. This is a package specific file that may go out to different URL or may change in the future where this package should NOT have to update to the URL, it has already been packaged. Having a URL here does not make sense to me.

[tools]
"http:my-script" = { version = "{{MISE_TOOL_VERSION}}", postinstall = "mv -v nebula-ca/build/{{os()}}-{{arch(x64='amd64', arm64='arm64')}}/* ." }

---

So I got it to this point. So with or without the post install attribute I get the same error:

[tools."http:my-script"]
version = "1.0.0"
url = "http://example.org"
postinstall = "mv -v nebula-ca/build/{{os()}}-{{arch(x64='amd64', arm64='arm64')}}/* ."

$ mise run package-arm64 package-x64 -- public
http:my-script@1.0.0  download                                                                                                                                                                       ◜
mise ERROR Failed to install http:my-script@1.0.0: failed to persist temporary file: Directory not empty (os error 39): Directory not empty (os error 39)
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

So it's definitely trying to reach out to that URL. I should not have to download something, I'm just running the package tasks, NOT the install task and even then this is "POST" install so the download already happened..

INFO  http:my-script@1.0.0  [1/3] install
INFO  http:my-script@1.0.0  [1/3] download 
DEBUG GET Downloading http://example.org/ to ~/.local/share/mise/downloads/http-my-script/1.0.0/
DEBUG GET http://example.org/
DEBUG Loaded netrc from /home/user/.netrc
DEBUG starting new connection: http://example.org/
DEBUG connecting to [2606:4700:10::ac42:9ded]:80
DEBUG connected to [2606:4700:10::ac42:9ded]:80
DEBUG GET http://example.org/ 200 OK
DEBUG pooling idle connection for ("http", example.org)
DEBUG [vfox] Getting metadata for yarn
DEBUG config: ~/dev/ipall/stacks/my-script/mise.toml
DEBUG config: ~/.config/mise/config.toml
Error: 
   0: Failed to install http:my-script@1.0.0: failed to persist temporary file: Directory not empty (os error 39): Directory not empty (os error 39)

[jcalfee]

I included in my project specific mise.toml file:

[settings]
experimental = true

[hooks]
postinstall = "mv -v nebula-ca/build/{{os()}}-{{arch(x64='amd64', arm64='arm64')}}/* ."

This did not work either. I see "experimental" on the top of the hooks page, but no warning or mention of having to add settings experimental = true.

[jcalfee]

I really don't care how it works. I was under the impression that mise could handle multi-platform builds. Claude can't do it, grok can't do it, gemini-3-flash-preview can't do it, glm-5.1 can't do it, and mise's AI coding assistant can't do it..

3. The deprecation warning is unrelated — somewhere in your tool config you have a URL template using {version} (single braces). Change it to {{ version }} (double braces with spaces). That warning isn't blocking the hook.

No, I do not think so. Somewhere in the code it re-reformat. I have the shared package file in conf.d and it is fine. The files on the http server are fine. I even re-run in docker to absolutely reset everything.