20260417T114310Z-feceee6

chore(golang): update to 1.26.2 (#221)

20260408T084910Z-570a4d4

Clarify an error message returned by the scheduler

This makes it more explicit that this is caused by a collision on the
worker ID.

20260331T121710Z-31166ae

Don't construct SymlinkFactory in the non-VFS case

Spotted by: @BoleynSu

20260330T204535Z-4c74907

Set ownership on symlinks created by build actions during their execu…

20260330T150045Z-8017f8f

Make HandleAllocatingSymlinkFactory respect the path format

It looks like we did add the function argument for it to its
constructor, but failed to patch up the implementation to actually use
it properly. There should be no calls to GetUNIXString() here.

20260330T095624Z-5f5d647

Bump the date at which we move to REv2.3 exclusively to 2028-01-01

In https://github.com/buildbarn/bb-remote-execution/pull/218 it was
brought up that Bazel 8.x remains supported until 2028-01-01. Let's
align the date at which we bump the deprecated API version to v2.3.0
with that.

20260326T163248Z-e6ab874

Remove support for REv2.0 and REv2.1 (#202)

* Remove support for REv2.0 output files/directories

On 2019-11-19, REv2 changed the way expected output paths are declared
in the Command message. It used to be the case that files and
directories were declared separately, but this prevents you from writing
an action that captures either of those, depending on what the action
generated.

Given that this feature was added 6.5 years ago, let's go ahead and
remove support for the old scheme. Clients have had more than enough
time to implement the new scheme.

* Remove support for platform properties in Command messages

REv2.2 promoted the platform properties from the Command message to the
Action message. This has the advantage that the scheduler no longer
needs to process any Command messages. This saves one round trip to the
CAS. Command messages can in some cases also become very large, meaning
it adds unnecessary memory pressure on the scheduler.

Given that this feature was added on 2020-10-17 and clients were able to
adopt quickly. it's time to remove support for the old scheme.

* Bump the deprecated API version to REv2.2

With support for REv2.0 and REv2.1 specific features removed, we should
go ahead and bump the deprecated API version to REv2.2. This will force
clients to stop using these old features, or simply stop working
altogether.

20260320T084040Z-59f12f4

Unbreak UserSettableSymlink

With #216 applied, the symlink implementation should no longer depend on
AttributeMaskSizeBytes at all. However, we should obtain the
authentication metadata from ctx in case the symlink target is
requested.

20260319T042723Z-cd89f05

Let symlinks be backed by path.Parser (#216)

20260318T200704Z-db78144

Upgrade all Go dependencies (#217)

On the bb-storage side we added support for ZSTD compressor/decompressor
pools. This requires us to add a similar option to bb_noop_worker,
bb_scheduler, and bb_worker.