Work on a strategy of synchronised imports of motoko-base
for moc
bumps
#2634
Replies: 5 comments
-
Sounds useful to me. @ericswanson-dfinity what do you think? |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
Maybe we can append my |
Beta Was this translation helpful? Give feedback.
-
Absolutely. |
Beta Was this translation helpful? Give feedback.
-
We now update See also https://github.com/dfinity/sdk/blob/master/nix/sources.json#L159 |
Beta Was this translation helpful? Give feedback.
-
We received a report (dfinity/motoko-base#392) that
motoko-base
was too new for the includedmoc
.Suggestion: we could tag (e.g.
moc-0.6.28
) the base library with a known-to-work label, and thedfx
import procedure could then be modified to always track that for amoc
bump.What do you think?
Beta Was this translation helpful? Give feedback.
All reactions