Skip to main content

Release r202606

What's new​

This release contains the following new or changed functionality:

In addition to these changes, this release contains a large number of internal improvements to the automator. These improvements do not change any functionality, but they pave the way for important upcoming features, such as increased insight in and control over package executions.

External database support for sql()​

The sql() function can now work with external databases in addition to the built-in in-memory database. By calling db_use() with the name of a MySQL account, all subsequent sql() calls are executed against that external database.

To use this, create an account of type "MySQL" with the connection details for your database.

db_use("mysql-account");

let rows = sql("SELECT * FROM customers WHERE active = ?", 1);
log("customers", rows);

For more information, see the (improved) database function documentation.

Absolute URLs in HTTP request functions​

The http_request(), http_request_file(), and http_stream_file() functions now support absolute URLs. Previously, the URL provided in the options was always appended to the account's endpoint URL. Now, if the URL starts with http:// or https://, it is used as-is without prepending the account endpoint.

This is useful, for example, when working with pre-signed URLs from cloud storage services like S3.

let options = {
  url: "https://my-bucket.s3.amazonaws.com/files/report.pdf",
  method: "GET",
};

let result = http_request_file(options, "http-account");

Improved package creation flow​

When creating a new package, you are now prompted to enter the package name first. This way, you can name your package upfront and then focus on writing the script, without later having to switch to the Settings tab to change the default name.

Add new package

HTTP and REST account types unified​

The REST account type has been merged into the HTTP account type. Existing REST accounts are automatically converted to HTTP accounts with the Content type field set to application/json.

All REST functions continue to work as before — no changes to existing packages are needed.

Timeline​

The deployments of the release will be performed on

EnvironmentDate
DemoFriday, February 28th
ProductionThursday, March 12th

The deployment of the Production environments will be conducted outside of office hours (Central European Time Zone).