Unison version upgrade

Programming Unison
1

Hi!

I think we have to try to upgrade the Unison version on the Unison track. I will try to experiment with it and put all results here. Now I have some questions:

  1. @ErikSchierboom As I found, if the track version was upgraded but some solutions use deprecated features, users have to manually edit their solutions to pass all tests again. Am I right?
  2. In the Dockerfile of the Unison test runner, I found the command that pulls dependencies from the “custom” namespace unison.public.exercism_tooling.pinnedLibVersions.baseV1_1_1 (unison-test-runner/Dockerfile at main · exercism/unison-test-runner · GitHub). Where can I find this namespace, @rlmark ?
2

Yes, that is correct.

3

Thank you!

4

Apologies for the delay. I’ve been mentioning this to the Unison team so it’s a known todo to get our Exercism track up to date. It’ll require some changes to the transcripts in each of the exercises in addition to changes to the script which sets up the Unison workspace. I’m working with the team to get an up to date docker build for the UCM executable now.

5 Likes
5

Great! I am a maintainer on the Unison track now. So if you have some tasks, feel free to provide them to me.

2 Likes
6

@SimaDovakin, thank you, this is amazing! Unison has been stretched pretty thin so it’s fantastic to have another maintainer! I’d be happy to give you a run-down on what would need to happen to upgrade the track. I haven’t had enough time to actually do it, but we basically need to change the track to support the “projects” model of Unison code. There’s also some fun stuff with changing the Json encoder/decoder that we’re using.

7

I did some experiments with the test runner upgrade. I will write down all results of my experiments here.