Rename the update step to publish

README.md

@@ -8,12 +8,12 @@ projects, in the same spirit as
 - `example-makefile.make` — project Makefile: local dev targets
   (`build`, `run`, `wasm`, `export`, `binaries`, `watch`, `clean`)
   plus the Woodpecker pipeline targets (`ci-version`, `ci-export`,
-  `ci-binaries`, `ci-upload`, `ci-update`).
+  `ci-binaries`, `ci-upload`, `ci-publish`).
 - `example-woodpecker.yaml` — Woodpecker pipeline: version → build
   (Rust, `wasm32-unknown-unknown` target + `wasm-bindgen` in the
   `git.teletypegames.org/internal/bevy-builder` image) → binaries
   (native linux-x64 + mingw win-x64) → upload (HTTP POST to `/build/upload`) →
-  update (calls the teletypegames `/build/publish` endpoint with
+  publish (calls the teletypegames `/build/publish` endpoint with
   `platform=bevy`).
 - `builder.Dockerfile` — the CI builder image: `rust:1-bookworm`
   (glibc — bevy's native linux build needs alsa/udev, which does not

example-makefile.make

@@ -128,8 +128,8 @@ ci-upload:
 			"$(UPDATE_SERVER)/build/upload?name=$(PROJECT)&version=$$VERSION" || exit 1; \
 	done
 
-ci-update:
+ci-publish:
 	@VERSION=$$(cat $(VERSION_FILE)); \
 	curl -fsS -X POST -H "X-Update-Secret: $(UPDATE_SECRET)" "$(UPDATE_SERVER)/build/publish?name=$(PROJECT)&platform=bevy&version=$$VERSION"
 
-.PHONY: all build run wasm export binaries binary-linux binary-win watch clean ci-version ci-export ci-binaries ci-upload ci-update
+.PHONY: all build run wasm export binaries binary-linux binary-win watch clean ci-version ci-export ci-binaries ci-upload ci-publish

example-woodpecker.yaml

@@ -27,7 +27,7 @@ steps:
       - apk add --no-cache make curl
       - make ci-upload
 
-  - name: update
+  - name: publish
     image: alpine
     environment:
       UPDATE_SERVER: https://teletypegames.org
@@ -35,4 +35,4 @@ steps:
         from_secret: update_secret_key
     commands:
       - apk add --no-cache make curl
-      - make ci-update
+      - make ci-publish