Work on a strategy of synchronised imports of motoko-base for moc bumps

[ggreif]

We received a report (caffeinelabs/motoko-base#392) that motoko-base was too new for the included moc.

Suggestion: we could tag (e.g. moc-0.6.28) the base library with a known-to-work label, and the dfx import procedure could then be modified to always track that for a moc bump.

What do you think?

[viviveevee]

Sounds useful to me. @ericswanson-dfinity what do you think?

[crusso]

It looks to me like dfx post 0.10.1 is just downloading the released moc tar ball from the release site it gets moc from which should reduce the risk.

It would be good to tag motoko-base appropriately too, perhaps just manually until we get add-tags.sh to work again.

I even started on a PR for adapting add-tags.sh but my git/bash foo was too poor
caffeinelabs/motoko#2926

[ggreif]

Maybe we can append my bar to your foo to get some full-fledged foobar? :-)

[crusso]

Absolutely.

[ghost]

We now update motoko-base and the moc binary based on the version: https://github.com/dfinity/sdk/blob/master/scripts/update-motoko.sh#L13

See also https://github.com/dfinity/sdk/blob/master/nix/sources.json#L159