Peter Thomas

@joelpramos good point. I think the karate-way to do that would be a `karate.callSingle()` that can call `karate.abortSuite()` (maybe we need it after all)

@joelpramos yes I meant calling `karate.abortSuite()` in `karate-config.js` but I see where you are coming from. it can be argued that `karate.callSingle()` is confusing and a more "feature compatible" way...

@joelpramos the suite is designed to be immutable, if you want the suite you can always do `Results.getSuite()` - but if you mean you want to set something, before the...

@joelpramos yeah, maybe the Runner should return a `Future`. we don't yet do a `build()` method like everybody else, maybe that is the way to go

1.3.0 released

done in `develop` and CI looks good

@julianladisch thanks, we will keep this open until the final 1.3.0 release, just the process we follow here

1.3.0 released

this was done to reduce memory usage and I agree this is inconsistent from `response` and `responseHeaders`. I propose we make this available via the new `karate.response` API, it may...

this is fixed. trying to get `karate.response` to work properly in a caller feature post a called feature doing an HTTP invoke was too much trouble, so decided to "promote"...