Browse Source

Update Urbit to v2.9 (#630)

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

2
urbit/docker-compose.yml

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

9
urbit/umbrel-app.yml

@ -2,7 +2,7 @@ manifestVersion: 1
id: urbit
category: Networking
name: Urbit
version: "v2.8"
version: "v2.9"
tagline: Run Urbit on your Umbrel
description: >-
Urbit is a personal server for self-sovereign personal & networked
@ -35,10 +35,7 @@ torOnly: false
submitter: ~mopfel-winrux
submission: https://github.com/getumbrel/umbrel/pull/1246
releaseNotes: >-
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.
A few days ago we discovered a performance issue when a remote scry publisher gets many simultaneous requests, as often happens during OTA updates. This performance bug caused the publisher to do 500x more work than necessary. We have now released vere-v2.9 to fix the issue.
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
Full release notes here: https://github.com/urbit/vere/releases/tag/vere-v2.9

Loading…
Cancel
Save