Arvados

Is this causing a specific bug right now? If so, does Workbench also need the upgrade?

I feel like we need to settle on some rule for updating and roll it into our process. This keep coming up; see ea5a4de11, 0975ea0b42e, b212abf2074 (all arvados-cli, but the same principle).

A specific (although minor) bug is that if the API server is using an old Ruby SDK gem, it will report invalid collection signatures as "missing" rather than "invalid".

Tom fixed the immediate issue in 50f8ae2. I'll leave this open for now to try to remind us to have the bigger conversation.