Skip to content

Releases: suborbital/reactr

Beta-9.1

24 Mar 12:53
12eae4d
Compare
Choose a tag to compare

This release contains an internal change to how bundles are written, no external or breaking changes.

Beta-9

20 Mar 16:30
5f33527
Compare
Choose a tag to compare

This release contains a huge internal improvement to how WebAssembly modules communicate with Reactr. Your Runnables will need to be re-compiled with the 0.9.0 libraries for Rust and Swift.

This release also improves the safety of the Rust Runnable crate by changing the return value of some functions to Result or Option. Please update your code accordingly.

WebAssembly Runnables are now more performant when accessing or returning large amounts of data, and the new internal system will make it easier to develop new features in the future.

Of note, two pieces of functionality are still missing from the Swift library compared to Rust:

  • Setting HTTP request and response headers
  • Ability to return errors from the run method

These will be added soon.

Beta-8.2

13 Mar 17:27
c9cad3d
Compare
Choose a tag to compare

This release improves the safety of the req::state method and the util::to_string method. It also adds req::state_raw for values that are not strings.

Beta-8.1

12 Mar 16:08
c8e9e23
Compare
Choose a tag to compare

Beta-8.1 brings the ability to set response headers from Wasm Runnables.

Using Rust, resp::set_header(key, val) will indicate to the caller that the module wants to set a Response header and the headers will be included in the job response.

This functionality only works when a CoordinatedRequest is mounted on the instance (by passing its JSON as the job data)

Beta-8

10 Mar 01:13
8366cf1
Compare
Choose a tag to compare

Welcome to Beta-8 of Reactr!

This release is a breaking change for Rust Runnables

Rust Runnables can now return errors! The signature of run has been changed to return Result<Vec<u8>, RunErr>, which allows propogating an error code and message to the caller. Consumers of Reactr can use errors.As to see if an error returned from a job is rt.RunErr, indicating that it was an error returned from a Runnable. Other error types indicate a failure to actually execute the Runnable in some way.

The Swift Runnable API will be updated in a future version to support returning errors.

Beta-7.1

02 Mar 13:17
v0.7.1
e96f02d
Compare
Choose a tag to compare

This release contains internal changes to the Directive format to support future Atmo features (schedules!)

No changes were made to the WebAssembly runtime, the Runnable API libraries remain at v0.6.3

Beta-7

24 Feb 13:52
v0.7.0
636d99d
Compare
Choose a tag to compare

The scheduler now has Schedules! Beta-7 brings the ability to register a Schedule object that will run jobs based on a schedule you define, such as "run after 1 minute" or "run every hour" or anything else you can think of!

The Schedule interface is very easy to implement for custom Schedules, and the Every and After Schedules are provided in the rt package.

Enjoy!

Beta-6.3

13 Feb 18:01
v0.6.3
ee788c9
Compare
Choose a tag to compare

This release contains some minor but important tweaks to memory management in the Swift library. You should update your Runnable versions to 0.6.3 for Swift and Rust and re-build.

No breaking changes to the FFI, so 0.6.3 runnables are backwards compatible when built.

Beta-6.2

13 Feb 03:14
v0.6.2
3129001
Compare
Choose a tag to compare

This version includes some minor improvements to static file access and the Wasm environment internals. No new Runnable API versions are needed, as there are no breaking changes. You should continue to use v0.6.0 of the crate and Swift package.

Beta-6.1

10 Feb 14:13
v0.6.1
a6edd20
Compare
Choose a tag to compare

This release contains an internal change to allow nested files within the static directory. It is not a breaking change, no need to update Runnable API.