install: point install.sh at hanzoai/pack releases

REPO_OWNER/REPO_NAME built the GitHub API and download URLs from
railwayapp/railpack, so the installer could never find a release under
this fork -- hanzoai/pack has never had one.

REPO_NAME did double duty as both the repository slug (used in the API
and download URLs, needs to be "pack") and the installed command name
(used by `which`/`rm` on uninstall, needs to stay "railpack", the actual
compiled binary name per .goreleaser.yml). Collapsing both into "pack"
would make uninstall run `which pack`, which on many machines resolves to
the unrelated Cloud Native Buildpacks CLI. Split it into REPO_NAME (repo
slug and archive-name prefix, matching the project_name pinned in
.goreleaser.yml) and a new BINARY_NAME (the installed executable), and
routed each use to the right one.

RELEASE.md's GHCR links and package-registry URLs updated to match.

Do not merge until hanzoai/pack has an actual release: push a v* tag once
the prior two commits are on main and the release workflow has published
the builder, runtime, and frontend images. Before that, the download URL
this script builds 404s by construction.

Co-authored-by: Hanzo Dev <[email protected]>

RELEASE.md

@@ -1,6 +1,6 @@
 # Release Process
 
-This document outlines the process for creating new releases of Railpack.
+This document outlines the process for creating new releases of Hanzo Pack.
 
 ## Creating a New Release
 
@@ -23,7 +23,7 @@ This document outlines the process for creating new releases of Railpack.
    workflow](https://github.com/hanzoai/pack/actions/workflows/release.yml)
    will automatically:
    - Build and publish the frontend Docker image to
-     [GHCR](https://github.com/orgs/railwayapp/packages?repo_name=railpack)
+     [GHCR](https://github.com/orgs/hanzoai/packages?repo_name=pack)
    - Create a GitHub release with changelog
    - Build and attach binaries for multiple platforms
 
@@ -42,9 +42,9 @@ git tag -d v0.18.0 && git push --delete origin v0.18.0 && git tag v0.18.0 origin
 The frontend Docker image is published to GitHub Container Registry (GHCR) with
 the following tags:
 
-- `ghcr.io/railpack/railpack-frontend:latest` (on default branch)
-- `ghcr.io/railpack/railpack-frontend:v1.2.3` (specific version)
-- `ghcr.io/railpack/railpack-frontend:1.2` (minor version)
+- `ghcr.io/hanzoai/pack-frontend:latest` (on default branch)
+- `ghcr.io/hanzoai/pack-frontend:v1.2.3` (specific version)
+- `ghcr.io/hanzoai/pack-frontend:1.2` (minor version)
 
 The image is built for both `linux/amd64` and `linux/arm64` platforms.
 
@@ -62,4 +62,4 @@ After pushing a tag:
 2. Verify the [GitHub release](https://github.com/hanzoai/pack/releases)
    is created with the correct artifacts
 3. Confirm the frontend Docker image is available in the [package
-   registry](https://github.com/railwayapp/railpack/pkgs/container/railpack-frontend)
+   registry](https://github.com/hanzoai/pack/pkgs/container/pack-frontend)

install.sh

@@ -1,9 +1,12 @@
 #!/usr/bin/env bash
 
 # Repository configuration
-REPO_OWNER="railwayapp"
-REPO_NAME="railpack"
+REPO_OWNER="hanzoai"
+REPO_NAME="pack"
 REPO_URL="https://github.com/${REPO_OWNER}/${REPO_NAME}"
+# the compiled binary is still named railpack (see .goreleaser.yml), distinct
+# from the repository name above
+BINARY_NAME="railpack"
 
 help_text="Options
 
@@ -418,7 +421,7 @@ if [ $UNINSTALL == 1 ]; then
   msg=""
   sudo=""
 
-  if test_writeable "$(dirname "$(which ${REPO_NAME})")"; then
+  if test_writeable "$(dirname "$(which ${BINARY_NAME})")"; then
     sudo=""
     msg="Removing railpack, please wait…"
   else
@@ -429,8 +432,8 @@ if [ $UNINSTALL == 1 ]; then
   fi
 
   info "$msg"
-  ${sudo} rm -f "$(which ${REPO_NAME})"
-  ${sudo} rm -rf /tmp/${REPO_NAME}
+  ${sudo} rm -f "$(which ${BINARY_NAME})"
+  ${sudo} rm -rf /tmp/${BINARY_NAME}
 
   info "Removed railpack"
   exit 0