v2.3.0-rc1

Retroactively tagging the v2.3.0 release.

This version contains a number of clarifications of the API, as well as two larger updates: the specification of compression for Bytestream transfers, and clarification on timeout handling for portions of the action that the individual caller has no control over (e.g., queuing).

v2.2.0

What's Changed

• Add Remote Asset API by @sstriker in #112
• use ASCII apostrophes in remote_asset.proto by @mostynb in #115
• fix typo in FetchBlob comment by @mostynb in #114
• ASCII-fy some more quotes in remote_asset.proto by @mostynb in #119
• be consistent with regards to emphasis by @mostynb in #120
• Use @bazel_remote_apis in readme by @Yannic in #122
• Clarify that servers should extend TLL for blobs referenced in FindMissingBlobs by @sstriker in #113
• Move output_node_properties from Action to Command by @juergbi in #121
• List EngFlow as another implementation by @ulfjack in #129
• Servers must provide empty blobs that weren't uploaded by @mostynb in #131
• Specify that stderr and stdout streams are resource names by @edbaunton in #116
• [remote asset api] Clarify resource_type by @sstriker in #126
• Field-based node properties by @juergbi in #128
• Add comments clarifying priority values by @peterebden in #145
• point out that servers may modify ActionResults, and mention one reason why by @mostynb in #106
• Drop canonicalization requirement for symlink targets by @juergbi in #142
• Add MurmurHash3 digest function by @erikmav in #146
• Add Please as a Remote Execution client by @peterebden in #158
• Add LogStream by @edbaunton in #148
• Add optional salt to Action by @erikmav in #149
• Standardize the terminology on lifetime instead of TTL by @vors in #150
• update generated go bindings for MurmurHash3 by @mostynb in #153
• GetActionResultRequest.inline_output_files description: consider output_paths by @santigl in #152
• include comments in generated *.pb.go for godoc by @atetubou in #161
• Add Flare to README.md by @zachgrayio in #169
• Clarify case-sensitivity of platform properties by @ulfjack in #172
• RemoteEx 2.2: Promote platform properties from command to action by @edbaunton in #167

New Contributors

• @sstriker made their first contribution in #112
• @ulfjack made their first contribution in #129
• @vors made their first contribution in #150
• @zachgrayio made their first contribution in #169

Full Changelog: v2.1.0...v2.2.0

v2.2.0-rc1

Retroactively tagging v2.2.0.

This version contains a number of clarifications in the API, as well as the transfer of platform properties field from the command proto to the action proto.

v2.1.0

What's Changed

• Add non-specific output_paths to Command to replace output_files and … by @ola-rozenfeld in #96

Full Changelog: v2.0.0...v2.1.0

v2.1.0-rc1

Retroactively tagging the v2.1.0 release.

This is marked rc1 just to test that the release-tagging mechanism is working correctly.

v2.0.0

First formal release of the RE API. From this point on, we will follow the semantic versioning requirements for API releases: all new fields and behaviours will result in a minor version bump; all backwards incompatible changes will result in a major version bump.

The Capabilities API low/high supported version reporting refers to the API release version tag.

Test release

PR #18 still needs to be merged, so this is not ready. Just checking how the release process works.

URLs (to be added to your WORKSPACE file):

• https://mirror.bazel.build/github.com/bazelbuild/remote-apis/archive/4ac001182e50d404fa790fb4a321daca089fe18c.tar.gz
• https://github.com/bazelbuild/remote-apis/archive/4ac001182e50d404fa790fb4a321daca089fe18c.tar.gz

SHA256: 874560dc65861624febd747c54b9ef70a1666e3d335e147ea362d1f331711057