Release v0.1.9

[alvin-reyes]

What's Changed

• uncomment staging bucket check by @en0ma in uncomment staging bucket check #387
• chore: revert filename to name by @alvin-reyes in chore: revert filename to name #389
• Constants package by @gmelodie in Constants package #381
• Quality of life changes for set up script by @snissn in Quality of life changes for set up script #397
• chore: fix constant variable calls by @alvin-reyes in chore: fix constant variable calls #400
• Add build and deploy workflows by @gmelodie in Add build and deploy workflows #401
• fix: application crashing on unverified client datacap by @arihantdaga in fix: application crashing on unverified client datacap #406
• fix pinning status for shuttle contents by @en0ma in fix pinning status for shuttle contents #378
• Correctly set data transfer failed status and message by @en0ma in Correctly set data transfer failed status and message  #377
• chore: added shuttle read-timeout config by @alvin-reyes in chore: added shuttle read-timeout config #409
• chore: sync dev with latest from master - 08232022 by @alvin-reyes in chore: sync dev with latest from master - 08232022 #412
• staging bucket and content manager refactor - part 1 by @en0ma in staging bucket and content manager refactor - part 1 #370
• feat: estuary modules/deps version bump by @alvin-reyes in feat: estuary modules/deps version bump #413
• Add basic usage docs to README.md by @travis in Add basic usage docs to README.md #414
• chore: sync dev with latest from master - 08242022 by @alvin-reyes in chore: sync dev with latest from master - 08242022  #416
• Add --disable-swagger-endpoint CLI flag by @gmelodie in Add --disable-swagger-endpoint CLI flag #422
• clarify difference between --no-storage-cron and --disable-deal-making by @toastts in clarify difference between --no-storage-cron and --disable-deal-making #388
• Add /public/miners/storage/query/:miner route to handleQueryAsk by @gmelodie in Add /public/miners/storage/query/:miner route to handleQueryAsk #423
• correctly check deal status and correctly restart transfers by @en0ma in correctly check deal status and correctly restart transfers #415
• Do not select shuttle if shuttle content adding is disabled by @en0ma in Do not select shuttle if shuttle content adding is disabled #427
• Make collections api restful by @gmelodie in Make collections api restful #426
• Document content/add response structure by @RangerMauve in Document content/add response structure #418
• Fix swagger annotation on delete miner endpoint by @gmelodie in Fix swagger annotation on delete miner endpoint #417

New Contributors

• @snissn made their first contribution in Quality of life changes for set up script #397
• @arihantdaga made their first contribution in fix: application crashing on unverified client datacap #406
• @travis made their first contribution in Add basic usage docs to README.md #414
• @toastts made their first contribution in clarify difference between --no-storage-cron and --disable-deal-making #388
• @RangerMauve made their first contribution in Document content/add response structure #418

Full Changelog: v0.1.8...v0.1.9

---

This discussion was created from the release v0.1.9.

[alvin-reyes]

Important notes

• This is the first release that will not be installed/deployed to shuttle-4 and shuttle-5. This means that we need to remove the content adding on these shuttles. As a primary option now, users who needs to upload should use https://upload.estuary.tech/content/add.
• The reason why we can't install on shuttle-4 and 5 is due to the version bumps. The version bump requires us to use a specific filecoin-ffi commit hash which doesn't compile on arm64 based operating system. Shuttle-4 and 5 are both arm64.
• I confirmed with @lanzafame that shuttles-4 and 5 are just for experimentation purposes. Given that this release has significant importance in the stability of estuary, I'm taking the route of not using arm64 operating system for new shuttles and just make shuttle-4, 5 as download/retrieval gateways with content-adding disabled. Slack discussion here.
• Moving forward, we will only update the api node, shuttles 1,2,6,7 and 8.

[gmelodie]

To add on to that, we do plan to eventually update shuttles 4 and 5, but only when filecoin-ffi starts offering support for arm64.