[](https://git.mokoconsulting.tech/MokoConsulting/MokoStandards) # Release Staging (RS) Server Deployment > **DEPRECATED (v04.06.00):** The `deploy-rs.yml` workflow has been **retired**. RS deployment is now handled exclusively through the release pipeline. Release artifacts are published via GitHub Releases (`auto-release.yml`) and distributed through platform-specific channels (Joomla `updates.xml`, Dolibarr `update.txt`). The `RS_FTP_*` variables and secrets are no longer used. ## Current Release Pipeline ``` dev → [alpha] → [beta] → rc → version/XX → main → dev optional optional ``` Production/RS deployment is achieved by: 1. **Joomla** — GitHub Release ZIP + SHA-256 + `updates.xml` with 5 stability entries (`development`, `alpha`, `beta`, `release-candidate`, `vXX`) 2. **Dolibarr** — GitHub Release + `update.txt` 3. **Generic** — GitHub Release There is no longer a separate SFTP deployment step to a release staging server. ## See Also - [Dev Deployment](dev-deployment.md) — development server (still active) - [Demo Deployment](demo-deployment.md) — demo server (still active) - [Auto Release](auto-release.md) — release pipeline that replaced RS deployment - [Release System](release-system.md) — end-to-end release lifecycle