Compare commits
6 Commits
e5ec81b172
...
main
| Author | SHA1 | Date | |
|---|---|---|---|
| f38dec2ac4 | |||
| 080f9827b8 | |||
| 7ac19a791c | |||
| b8306dcdaf | |||
| 08a4973bde | |||
| 8b8896f54b |
@@ -157,6 +157,21 @@ jobs:
|
||||
docker push "${IMAGE}:latest"
|
||||
docker push "${IMAGE}:${TAG}"
|
||||
|
||||
- name: Remove this run's image and cap the build cache
|
||||
# The build runs on the HOST daemon, so whatever it leaves stays on the
|
||||
# runner host for good: every run used to leave two tagged images, and
|
||||
# each newer `latest` turned the previous one into a permanent `sha-` image
|
||||
# until the host ran out of disk. Both tags are in the registry by now, so
|
||||
# the local copies are dead weight. BuildKit keeps its layer cache apart
|
||||
# from the images, so the next build stays fast; the cache is pruned to a
|
||||
# cap instead of growing forever (`--reserved-space` is the same flag's
|
||||
# name on newer Docker). Runs even after a failure, and never fails the job.
|
||||
if: always()
|
||||
run: |
|
||||
docker image rm "${IMAGE}:latest" "${IMAGE}:${TAG}" 2>/dev/null || true
|
||||
docker builder prune -f --keep-storage 5GB \
|
||||
|| docker builder prune -f --reserved-space 5GB || true
|
||||
|
||||
- name: Log out
|
||||
if: always()
|
||||
run: docker logout "${REGISTRY}" || true
|
||||
@@ -207,3 +222,11 @@ jobs:
|
||||
echo "::error::The site did not become healthy within 150s."
|
||||
docker compose logs --tail 100 site
|
||||
exit 1
|
||||
|
||||
- name: Remove the image this deploy replaced
|
||||
# The pull moves `latest` to the new image and leaves the old one untagged
|
||||
# on the host. Untagged images are never used again (a rollback pulls a
|
||||
# `sha-` tag from the registry), so drop them. Dangling images only: nothing
|
||||
# tagged and nothing a container is using is touched.
|
||||
if: always()
|
||||
run: docker image prune -f || true
|
||||
|
||||
2
PLAN.md
2
PLAN.md
@@ -956,6 +956,8 @@ deliberately so — no fetch can tell whether an APK runs. `checkFacts.mjs` asse
|
||||
still exist and that `minSdk` still says what "Android 10 or newer" claims, so the link is correct
|
||||
the moment a working build flips the boolean. The panel is not removed while the link is off: a page
|
||||
that omitted sideloading would read, to somebody who knows the APK exists, as a page hiding it.
|
||||
*(2026-10-31: the link is back on. Android `v0.7.0`'s APK was installed on an Android 16 emulator,
|
||||
connected to the public demo and read its Rust servers, so `serviceable` is `true`.)*
|
||||
|
||||
**Three mechanisms this phase added that the plan did not anticipate.**
|
||||
|
||||
|
||||
@@ -30,7 +30,8 @@ browsing the window.
|
||||
## Reports
|
||||
|
||||
Reports raised by members about Team forum threads and posts and, where a game module offers
|
||||
it, the game's chat lines — the Rust module does, from the `⋯` menu on a chat line. Each report keeps a copy of what the item said when it was
|
||||
it, the game's chat lines — the Rust module does, from the `⋯` menu on a chat line on the
|
||||
site and a long press in the [app](/app/). Each report keeps a copy of what the item said when it was
|
||||
reported, so an author editing it afterwards does not change what staff read. Three design
|
||||
decisions show through in how this screen behaves:
|
||||
|
||||
|
||||
@@ -128,6 +128,22 @@ export const appFeatures = [
|
||||
'Visible to the account they belong to and to nobody else.',
|
||||
gate: 'A game module',
|
||||
},
|
||||
{
|
||||
title: 'Report, block and hide',
|
||||
body:
|
||||
'Long-press a chat line to report it to the site’s staff, hide it for yourself, or ' +
|
||||
'block the player. A block is kept on your account, so it applies on the website and ' +
|
||||
'on every device too; staff cannot be blocked, and Account → Blocked undoes any of ' +
|
||||
'it. Staff get Hide for everyone on the same menu.',
|
||||
gate: 'A game module whose chat lines can be reported (Rust)',
|
||||
},
|
||||
{
|
||||
title: 'Deleting your account',
|
||||
body:
|
||||
'From My account, with your password and, where the account has one, a two-factor ' +
|
||||
'code. The account is deleted on the deployment at once — see what that removes and ' +
|
||||
'what it keeps on the delete-account page.',
|
||||
},
|
||||
],
|
||||
},
|
||||
{
|
||||
|
||||
@@ -27,7 +27,7 @@
|
||||
],
|
||||
"releases": {
|
||||
"installer": "v0.8.1",
|
||||
"Android-app": "v0.6.0",
|
||||
"Android-app": "v0.7.0",
|
||||
"link": "v2.3.0",
|
||||
"Module-uo": "v1.4.1",
|
||||
"Rust-Link": "v0.3.0",
|
||||
@@ -120,17 +120,18 @@
|
||||
"",
|
||||
"`serviceable` is the one value here with no authority to check it against, and it is",
|
||||
"deliberately manual. It answers a question no API can: does the published build",
|
||||
"actually work. The org lead reports v0.5.0's does not, so the download block renders a",
|
||||
"'being replaced' state instead of a link, and flipping this to true is the single edit",
|
||||
"that turns the link back on once a working build is released. A check cannot run an",
|
||||
"APK; a person can, and this is where they record that they did."
|
||||
"actually work. v0.5.0's did not, and while false the download block renders a 'being",
|
||||
"replaced' state instead of a link. A check cannot run an APK; a person can, and this",
|
||||
"is where they record that they did. v0.7.0's was installed on an Android 16 emulator",
|
||||
"on 2026-10-31, connected to the public demo and read its Rust servers: true.",
|
||||
"When `asset` moves to a new release, set this back to false until someone has run it."
|
||||
],
|
||||
"androidApk": {
|
||||
"asset": "runic-gateway-0.6.0.apk",
|
||||
"asset": "runic-gateway-0.7.0.apk",
|
||||
"checksums": "SHA256SUMS",
|
||||
"minSdk": 29,
|
||||
"minAndroid": "10",
|
||||
"serviceable": false
|
||||
"serviceable": true
|
||||
},
|
||||
|
||||
"gitea": {
|
||||
|
||||
Reference in New Issue
Block a user