[ANNOUNCE] vere-v1.16

[Peter McEvoy]

Arvo 417K
Vere 1.16

Description

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

• Add support for optimized and debug builds by @mcevoypeter in #103
• Create universal binary for 1.16 x86_64-darwin by @mcevoypeter in #91
• Upload 1.16 binaries to old bootstrap.urbit.org endpoints by @mcevoypeter in #87
• Correctly cast hun_y when trimming newlines in u3_king_next() by @mcevoypeter in #82
• Point binary upgrade system back to https://bootstrap.urbit.org/vere by @mcevoypeter in #80
• Document build system's dependency on automake and libtool on Linux by @mcevoypeter in #79
• Correct upload of Docker image by @mcevoypeter in #77
• Uncomment U3_OS_ARCH on macos-aarch64 by @mcevoypeter in #75
• Overwrite binaries deployed to soon and edge trains by @mcevoypeter in #73
• Make release pipeline resilient to newline in pkg/vere/VERSION by @mcevoypeter in #71
• Upload the latest binary version number to GCP by @mcevoypeter in #69
• Temporarily disable fake ship tests by @mcevoypeter in #67
• Test release of 1.16 by @mcevoypeter in #65
• Resolve URL discrepancies in binary upgrade system and CI by @mcevoypeter in #63
• Point binary upgrade system to bootstrap.urbit.org/vere-test by @mcevoypeter in #60
• Switch from tag-based release flow to push-based release flow by @mcevoypeter in #54
• Replace arm64 with aarch64 as canonical identifier for 64-bit ARM architecture by @mcevoypeter in #52
• Fix musl libc toolchain cache access by @mcevoypeter in #53
• Fix musl libc toolchain cache access by @mcevoypeter in #50
• Switch from tag-based release flow to push-based release flow by @mcevoypeter in #48
• Self-host M1 macOS GitHub Actions runner by @mcevoypeter in #46
• bazel-based continuous integration flow by @matthew-levan in #21
• Migrate git history from Urbit monorepo by @mcevoypeter in #38
• Build with musl instead of glibc on Linux by @mcevoypeter in #27
• Replace Xcode-specific sys_includes path in clang-macos-arm64 by @mcevoypeter in #24
• Build with bazel on darwin-x86_64 by @matthew-levan in #18
• Build with bazel on darwin-arm64 by @matthew-levan in #13
• Build with bazel on linux-arm64 by @mcevoypeter in #16
• Build with bazel on linux-x86_64 by @mcevoypeter in #10

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

--

~fanfun-mocbud

https://tlon.io

[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]

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]

The previous tars would extract into this (for example):

    urbit-v1.15-x86_64-linux/
    urbit-v1.15-x86_64-linux/urbit*

The 1.16 tar extracts into this:

    vere-v1.16-linux-x86_64*

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]

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.

—

~dovsem-bornyl

https://tlon.io