Files
modeling-app/rust
Adam Chalmers c25dfabc94 Stronger types and better error handling in executeMock (#7370)
This brings the `execute_mock` function into line with the `execute` function, which I tweaked in https://github.com/KittyCAD/modeling-app/pull/7351. Now mock execution, like real execution, will always return a properly-formatted KCL error, instead of any possible JS value.

Also, incidentally, I noticed that send_response always succeeds, so I changed it from Result<()> to void.
2025-06-04 18:24:24 -04:00
..
2025-03-13 23:38:41 -07:00
2025-06-03 22:04:56 -04:00
2025-06-03 22:04:56 -04:00
2025-06-03 22:04:56 -04:00
2025-03-04 22:21:12 -08:00

Rust Crates

Releasing

  1. Make sure your working directory is this directory.
  2. Bump the versions of the crates:
    just bump-kcl-crate-versions 
    
  3. Commit the changes:
    git add .
    git commit -m "Bump versions"
    
  4. Push the changes and get your PR approved.
  5. Publish the crates:
    just publish-kcl {version}
    
    • This will publish the relevant crates and push a new tag with the prefix kcl-. DO NOT SET THE PREFIX TO kcl- when you run the command. The just command will do that for you.
    • The tag will then trigger the release of kcl-python-bindings and kcl-language-server.