release: urbit-os-v1.0.29

MAINTAINERS.md

@@ -162,14 +162,15 @@ so that I can type e.g. `git mu origin/foo 1337`.
 If you're making a Vere release, just play it safe and update all the pills.
 
 For an Urbit OS release, after all the merge commits, make a release with the
-commit message "release: urbit-os-v1.0.xx".  This commit should have an
-up-to-date solid pill.  If neither the pill nor the JS need to be updated (e.g
-if the pill was updated in the previous merge commit), consider making the
-release commit with --allow-empty.
+commit message "release: urbit-os-v1.0.xx".  This commit should have up-to-date
+artifacts from pkg/interface and a new solid pill.  If neither the pill nor the
+JS need to be updated (e.g if the pill was already updated in the previous merge
+commit), consider making the release commit with --allow-empty.
 
 If anything in `pkg/interface` has changed, ensure it has been built and
-deployed properly.  For most things, it is sufficient to run `npm install; npm
-run build:prod` in `pkg/interface`.
+deployed properly.  You'll want to do this before making a pill, since you want
+the pill to have the new files/hash.  For most things, it is sufficient to run
+`npm install; npm run build:prod` in `pkg/interface`.
 
 However, if you've made a change to Landscape's JS, then you will need to build
 a "glob" and upload it to bootstrap.urbit.org.  To do this, run `npm install;

bin/solid.pill

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3027176667ec79c666fa63622c8d72d9f032bcc04653ba9791f027340782757e
-size 6270089
+oid sha256:463039d83a55c7a560101bda1614a6501ef8b0cc91144588cb372f36d1b42486
+size 6259468

pkg/arvo/app/glob.hoon

@@ -1,7 +1,7 @@
 /-  glob
 /+  default-agent, verb, dbug
 |%
-++  hash  0v5.8ftoc.8afop.f4kkn.r4kil.lk95a
+++  hash  0v2.kf979.bjv2a.i15f0.sesik.9nnot
 +$  state-0  [%0 hash=@uv glob=(unit (each glob:glob tid=@ta))]
 +$  all-states
   $%  state-0

pkg/arvo/sys/vane/clay.hoon

@@ -1005,6 +1005,15 @@
     =+  ezy=?~(ref ~ (~(get by haw.u.ref) mun))
     ?^  ezy
       :_(fod.dom.red `(bind u.ezy |=(a/cage [%& a])))
+    ?:  ?=([%s [%ud *] %late *] mun)
+      :_  fod.dom.red
+      ^-  (unit (unit (each cage lobe)))
+      :^  ~  ~  %&
+      ^-  cage
+      :-  %cass
+      ?~  let.dom
+        !>([0 *@da])
+      !>([let.dom t:(~(got by hut.ran) (~(got by hit.dom) let.dom))])
     =+  nao=(case-to-aeon case.mun)
     ?~(nao [~ fod.dom.red] (read-at-aeon:ze for u.nao mun))
   ::
@@ -3469,11 +3478,7 @@
           %open
         ``open+!>(prelude:(ford:fusion static-ford-args))
       ::
-          %late
-        :^  ~  ~  %cass
-        ?~  let.dom
-          !>([0 *@da])
-        !>([let.dom t:(~(got by hut.ran) (~(got by hit.dom) let.dom))])
+          %late  !!  :: handled in +aver
       ==
     ::  +read-t: produce the list of paths within a yaki with :pax as prefix
     ::