Skip to content

Commit

Permalink
Temporary workaround: Don't use DEFAULT word in ===
Browse files Browse the repository at this point in the history
There's an issue where DEFAULT as the first word wins a lookback.

This needs looking at, but is blocking a commit.  Workaround.
  • Loading branch information
hostilefork committed Jan 31, 2024
1 parent 4eb90e7 commit 17d1892
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions scripts/latest-of.reb
Original file line number Diff line number Diff line change
Expand Up @@ -143,7 +143,7 @@ latest-of: func [
print warning
]

=== DEFAULT OS TO VERSION RUNNING THIS SCRIPT (OR OS RUNNING BROWSER) ===
=== 'DEFAULT OS TO VERSION RUNNING THIS SCRIPT (OR OS RUNNING BROWSER) ===

; If you are running the web build and don't ask for a variant, the most
; sensible thing to do is to try and give you a version matching your
Expand Down Expand Up @@ -226,7 +226,7 @@ latest-of: func [
let extension: if (find [0.3.1 0.3.40] os) [".exe"] else [null]


=== DEFAULT VARIANT TO DEBUG ===
=== 'DEFAULT VARIANT TO DEBUG ===

; All stakeholders are requested to use debug builds unless they have a
; really good reason not to. The term "checked" may wind up preferred to
Expand All @@ -244,7 +244,7 @@ latest-of: func [
let suffix: if variant = 'release [null] else [join "-" variant]


=== DEFAULT COMMIT TO THE LAST GREEN-LIT HASH ===
=== 'DEFAULT COMMIT TO THE LAST GREEN-LIT HASH ===

; After a build is validated (and verified as being a completed upload), a
; file called %last-deploy.short-hash is updated in the build directory.
Expand Down

0 comments on commit 17d1892

Please sign in to comment.