[ANNOUNCE] vere-v1.16

Skip to first unread message

Peter McEvoy

Jan 13, 2023, 1:13:15 PM1/13/23
to urbit-dev

Arvo 417K
Vere 1.16


This release is functionally equivalent to v1.15 but is built in the new Vere repo using Bazel instead of Nix with a new and improved release pipeline. It marks the successful extraction of the runtime from the Urbit monorepo. It also adds a new AArch64-specific macOS build and removes the Windows build.

What's Changed

Full Changelog: urbit-v1.15...vere-v1.16




Peter McEvoy

Jan 13, 2023, 4:57:34 PM1/13/23
to urbit-dev, Peter McEvoy
This wasn't clearly communicated in the above email, but as part of this change, the Docker Hub repo has changed from https://hub.docker.com/repository/docker/tloncorp/urbit to https://hub.docker.com/repository/docker/tloncorp/vere. However, there's an issue with the v1.16 Docker image, so tloncorp/vere:latest is an alias for tloncorp/urbit:latest for now. Concretely, this means any ships running via Docker are confined to v1.15 until the issue with the v1.16 image is resolved.

Peter McEvoy

Jan 13, 2023, 6:37:30 PM1/13/23
to urbit-dev, Peter McEvoy
There's also an issue with the v1.16 linux-aarch64 build. The tracking issue can be found here, and the resulting fix can be found here. The fix will land in the next release, so if you're running on linux-aarch64, please remain on 1.15 until 1.17 goes out.

John Franklin

Jan 17, 2023, 10:12:45 PM1/17/23
to urbit-dev, Peter McEvoy
The previous tars would extract into this (for example):


The 1.16 tar extracts into this:


That's quite a mouthful and will break the docs
on every version bump.

Should we go back to the previous naming convention?

Zach Alberico

Jan 17, 2023, 11:09:49 PM1/17/23
to John Franklin, urbit-dev, Peter McEvoy
Hi John,

It won't break the docs, self-hosted users should be running upgrading their runtimes via .run, docked binaries, and the next command.

I recently updated the getting-started guide to make this clear (see step 5): https://urbit.org/getting-started/cli but this has been live since version 1.9 of the runtime.

When running upgrades with next and starting the ship with .run, the binary name is not needed.

For the initial boot, the curl commands in that guide rename the binary to "urbit", but after that .run and 'next' should be used.



Reply all
Reply to author
0 new messages