Skip to content
Mar 11, 2019

v142

Also print the change warning when the build fails (#639)
Mar 11, 2019

v141

Add temporary warning about "run build" change (#636)
* Add temporary bright warning about breaking change
Mar 11, 2019

v140

Run the build script by default (#628)
* Run the build script by default

This removes the opt-in behavior and defaults users into running
the "build" script by default. Users that were opted-in will see
no change
Mar 4, 2019

v139

Make breaking change warning header brighter
Feb 21, 2019

v138

Fix yarn run error when script is empty string (#624)
* Fix yarn run error when script is empty string
Feb 14, 2019

v137

Generate UUIDs for the app and build (#621)
This generates random uuids for both each build run, and the app itself. It then propagates the app uuid through each subsequent build by serializing it into the cache.

This isn't completely ideal because PR apps will each get their own app uuid, but it should still allow us to do better analysis on our log data than we currently can.

Questions like "How many apps failed yesterday?" vs "How many builds failed yesterday"?

The build uuid helps make sure that we aren't ever double counting events somehow.
Feb 9, 2019

v136

Add warning for the upcoming run build change (#616)
* Add warning for the upcoming run build change
Jan 28, 2019

v135

Make sure that failing builds in CI actually fail (#613)
Make sure that failing builds in CI actually fail
Dec 20, 2018

v134

fix: handle case where memory.limit_in_bytes is nonsensically large (#…
…531)

* fix: handle case where memory.limit_in_bytes is nonsensically large

In certain CI environments, this value can be misreported, resulting in an invalid initial `MEMORY_AVAILABLE` value. In these cases, we default the max detected memory to 16GB, or slightly larger than a `performance-l` instance.
Nov 28, 2018

v133

Add warning for flatmap-stream 404 failure (#590)
Add warning for flatmap-stream 404 failure
You can’t perform that action at this time.