Changelog
This page contains important changes to the Skybear.NET platform, including major breaking ones and selected non-breaking ones and highlights.
2024-Sep-21 — All response bodies automatically persisted and available
Super release today for Skybear.NET. 🚀 Automatically, all response bodies are stored, and you can retrieve them any time when debugging your script runs.
The output option continues to work, as well! We don’t break your scripts! Ever.
In cases where your script has an output option specified, the response body will be stored twice, one under the value of your output option, and one that is autogenerated by the platform.
For example, the following script will persist the response bodies shown further below:
GET https://api6.ipify.org?format=json[Options]output:test-https-ipv6.jsonrepeat: 3HTTP 200
GET https://unpkg.com/[email protected]/dist/preact.min.js[Options]output:test-preact.min.jsHTTP 200Script run report:
Output resources:Entry 1 - test-https-ipv6.json ➥ (0.041 kb)Entry 3 - test-preact.min.js ➥ (11.435 kb)
Response bodies:Entry 1 - 5de1a444-3d1e-4100-a098-00fca0902d92_response.json ➥ (0.041 kb)Entry 1 - e5d11439-b125-42d8-828f-bb26e47eb00a_response.json ➥ (0.041 kb)Entry 1 - 34c9a327-6190-44ff-938a-646a85e67462_response.json ➥ (0.041 kb)Entry 3 - 1ae6dc58-e97b-42b3-b662-e3eeaa58fc26_response--preact.min.js ➥ (11.435 kb)Each request/response expandable widget, will also link its corresponding response body for you to inspect if necessary.
Social media posts: Twitter | LinkedIn
2024-Sep-10 — Script executors moved out of AWS Lambda
Before this release, our script executors were running on AWS Lambda, that has IPv6 restrictions (see known-issue for more details).
Today, we moved the executors out of AWS Lambda, and into Fly.io. This means you can pretty much run your scripts almost exactly as you can do locally.
Restrictions on accessing addresses on localhost still apply though 😏 Don’t be evil!
Social media posts: Twitter
2024-Sep-08 — Hurl upgrade to 5.0.1
The Hurl version executing scripts from now on is Hurl 5.0.1.
This is a non-breaking change for your scripts.
There are some niceties added by the Hurl team like the flexible time units and better errors (see announcement).
Scripts using Hurl variables are not yet runnable through the UI, but support for storing secret Hurl environment variables at the account level is coming soon.
Social media posts: Twitter
2024-Sep-01 — Manage Hurl variables natively in the UI
Finally, Hurl variables are fully integrated in the platform! In the UI and the HTTP/Cron triggers. 🥳
You can define them in your Skybear.NET account secrets page, and use them across all your scripts.
All Hurl variables are being treated as sensitive secrets. Never logged or stored in plaintext. 🔐 Script run reports are also encrypted. How your scripts use them is up to you though.
I do Envelope encryption. Each variable is encrypted with its own Data encryption key (DEK), that itself is encrypted with a Key Encryption Key (KEK) for each account, and that KEK finally {en,de}crypted by AWS KMS!
Now you can literally take your local scripts, put them in Skybear.NET, and run them in the UI, or configure them to run automatically every few minutes, or even get an HTTP URL that you can invoke in your CI and have them running in the Skybear platform remotely.
Let me know if you have any feedback. 😎
Social media posts: Twitter | LinkedIn
2024-Aug-17 — Pass Hurl variables to HTTP trigger runs
Pass Hurl environment variables to your scripts when using HTTP trigger, allowing fully dynamic scripting. 🥳
Super nice feature, and also a stepping stone for full CI support, i.e. running your scripts from your own CI workflows, or anywhere really, without sacrificing functionality or having to do any changes to them.
Social media posts: Twitter | LinkedIn
2024-Aug-11 — HTTP trigger
Trigger your scripts by sending a POST request to a special URL.
You can now run your scripts from your CI, and integrate them in whatever workflow you already have outside the Skybear.NET platform.
Please treat the HTTP trigger URL as sensitive data, as you would any other secret, since anyone that sends a POST request to that URL will be triggering a run of your script.
Social media posts: Twitter | LinkedIn
2024-Jul-17 — Skybear.NET pricing page
After several days of work, and a few weeks of vacation, we are open for business! 🚀
Pricing information at https://about.skybear.net/pricing.
I spent a lot of time thinking about the billing model, and the number of step requests seemed the best. It is fair for me, since that’s one of the main dimensions of the platform costs (in addition to the duration of your script).
And I consider it a nice dynamic dimension for the users as well, since it does not force you into a weird usage where you try to reduce number of scripts, or number of steps within a script, and other funny annoying approaches I see in other platforms.
It’s definitely the first iteration, and I will be closely looking into improving it over time, especially as usage ramps up, and I see what’s actually more beneficial for the user.
If you have feedback, please reach out. Complaints are also welcome, as long as they are relevant 😅
Social media posts: Twitter | LinkedIn
2024-Jun-13 — Skybear.NET landing page
After a few days of iteration and plenty of small UI touches, we now have the Skybear.NET landing page ready for the world to see 😁
Visit https://about.skybear.net and let us know what you think!
More documentation on features, examples, and pricing soon!
Social media posts: Twitter | LinkedIn
2024-Jun-06 — Scheduled runs email notifications
The new email notifications when your script runs fail fully enables you to use Skybear.NET for monitoring purposes.
Monitor your HTTP API continuously, and get an email the second it fails! 👌
Social media posts: Twitter | LinkedIn
2024-May-25 — Scheduled runs cron trigger
Schedule your scripts to run periodically every few minutes, or on specific dates, using standard cron expressions.
Notifications will follow soon! Have fun 🎉
Social media posts: Twitter | LinkedIn
2024-May-11 — Historical script runs list page
See historical runs of your script, including access to the source code of that exact run, and to all the output resources you persisted in that execution. Current retention is 30 days.
Visit https://www.skybear/net/scripts to view all your scripts, and then for each script you can view all its script runs at https://www.skybear/net/scripts/<scriptID>/runs (or click the View past run results button while at the script details page). 🎉
Social media posts: Twitter | LinkedIn
2024-May-07 — Output option to store responses
Since Hurl 4.2.0 (read their annoucement blog), there was the output option that allows someone to locally persist the full response of a request made by the script.
We now natively support this option, and any output file is automatically uploaded onto our platform, and is accessible to you later every time you open the script run report.
Example script using the output option:
GET https://about.skybear.net/_live-demo/get.json[Options]output: call1-get.jsonHTTP 200Running the above script will create a file call1-get.json, and will be available in the script run report for download.
Social media posts: Twitter | LinkedIn
2024-Apr-27 — Hurl upgrade to 4.3.0
Upgraded the Hurl version used on the Skybear.NET platform to 4.3.0.
See the full Hurl changelog at their Github release page, and read their annoucement blog.
2024-Apr-25 — Historical script runs
Starting today, you can access previous script runs results.🎉 All script runs by signed-in users are retained for 1 month.
Social media posts: Twitter
2024-Feb-24 — Hurl upgrade to 4.2.0
Upgraded the Hurl version used on the Skybear.NET platform to 4.2.0.
See the full Hurl changelog at their Github release page, and read their annoucement blog.
2024-Feb-18 — Private accounts for managing scripts
Rebranded from webscripts.lambrospetrou.com to skybear.net.
Introduced the private user accounts for creating, authoring, and running Hurl scripts.
Manage your scripts at https://www.skybear.net/scripts.
Social media posts: Twitter | LinkedIn
2023-Sep-28 — Initial release v0.0.1
The first publicly announced release of the initial version of Skybear.NET, under a subdomain on my personal website, webscripts.lambrospetrou.com.
It included the Open Editor, and the network requests timeline widget, alongside Hurl reports.
Launched using Hurl version v4.1.0.
It is still very early stages, and I have many features on the roadmap to be shipped over the next few months.
It does the job though. You write a Hurl script, click “Run script” and off you go. In a few milliseconds you will get back the results, along with the full report of your script’s requests.
You can also share your script with your friends and colleagues to show off your awesome tests.
Hurl scripts are declarative HTTP requests, where you can do assertions on the response, capture values and use them in follow-up requests, and plenty more.