Browse Source

Update Urbit to v2.8 (#614)

main
reid 2 years ago
committed by GitHub
parent
commit
128740b1bc
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
  1. 2
      urbit/docker-compose.yml
  2. 14
      urbit/umbrel-app.yml

2
urbit/docker-compose.yml

@ -7,7 +7,7 @@ services:
PROXY_AUTH_ADD: "false"
manager:
image: mopfelwinrux/urbit-umbrel:v2.6@sha256:0e0527fd2b2363301e4ea58094f24a7452b8ef6075142ee21a0a42cb4deb51ca
image: mopfelwinrux/urbit-umbrel:v2.8@sha256:e9570fb3b52958a55f84cf96bee7eae809ded459d3be924cd3e09c06f9c6bfbf
ports:
- "34343:34343"
volumes:

14
urbit/umbrel-app.yml

@ -2,7 +2,7 @@ manifestVersion: 1
id: urbit
category: Networking
name: Urbit
version: "v2.6"
version: "v2.8"
tagline: Run Urbit on your Umbrel
description: >-
Urbit is a personal server for self-sovereign personal & networked
@ -35,8 +35,10 @@ torOnly: false
submitter: ~mopfel-winrux
submission: https://github.com/getumbrel/umbrel/pull/1246
releaseNotes: >-
This vere release fixes an issue where accessing a previously removed
Eyre et-response in-memory cache path would cause a ship to crash.
Full release notes here: https://github.com/urbit/vere/releases/tag/vere-v2.6
The previous release vere-v2.7 introduced a regression presenting as a significant disk read increase when swapping. This issue was caused by a flag meant only for development builds being set in the release build, causing every snapshot write to do an overly paranoid check on snapshot integrity.
We have now released vere-v2.8 to fix the issue.
Full release notes here: https://github.com/urbit/vere/releases/tag/vere-v2.8

Loading…
Cancel
Save