From d9303fa22c3dc90930b901d3ea2cb4267afa9fc3 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" <179508745+promptless[bot]@users.noreply.github.com> Date: Thu, 4 Dec 2025 20:09:35 +0000 Subject: [PATCH 1/3] Add GitHub rollback documentation for serverless endpoints --- serverless/workers/github-integration.mdx | 50 +++++++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/serverless/workers/github-integration.mdx b/serverless/workers/github-integration.mdx index 54bd0217..7dfbdaa7 100644 --- a/serverless/workers/github-integration.mdx +++ b/serverless/workers/github-integration.mdx @@ -88,6 +88,56 @@ You can monitor your build status in the **Builds** tab of your endpoint detail | Completed | Runpod completed the build and upload. | | Failed | Something went wrong (check build logs). | +## Roll back to a previous build + +Roll back your endpoint to any previous build directly from the Runpod console. This restores your endpoint to an earlier version without waiting for a new GitHub release. + +### Requirements + +To roll back an endpoint, you need: + +- An existing endpoint deployed with GitHub integration. +- At least one previous build available in your deployment history. + +### Roll back a deployment + +To roll back your endpoint to a previous build: + + + +Open the endpoint details page in the [Serverless section](https://www.console.runpod.io/serverless) of the Runpod console. + + + +Click the **Builds** tab to view your deployment history. + +Find the build you want to roll back to, then click the three dots menu button next to that build. + + + +Select **Rollback** from the menu. + +Review the confirmation modal and click **Confirm** to proceed with the rollback. + + + +After confirming, your endpoint rolls back to the selected build. A banner appears at the top of the endpoint page indicating the endpoint is on a rolled-back version. + + + +The rollback banner only appears when your endpoint is actively using a previous build version. Once you push a new commit and create a release, the banner disappears and your endpoint uses the new build. + + + +### Understanding rollback behavior + +When you roll back an endpoint: + +- Your endpoint immediately switches to the Docker image from the selected previous build. +- The rollback banner displays at the top of your endpoint page to indicate the current state. +- Your endpoint remains on the rolled-back version until you deploy a new release from GitHub. +- When you push a new commit and create a release, the new build automatically becomes the active version and supersedes the rollback. + ## Updating your endpoint When you make changes to your GitHub repository, they won't automatically be pushed to your endpoint. To trigger an update for the workers on your endpoint, create a new release for the GitHub repository. From dcf001e8d3700149cb224082f719449f2f713fb4 Mon Sep 17 00:00:00 2001 From: Mo King Date: Thu, 4 Dec 2025 15:14:42 -0500 Subject: [PATCH 2/3] Add beta tag & move rollback section --- serverless/workers/github-integration.mdx | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/serverless/workers/github-integration.mdx b/serverless/workers/github-integration.mdx index 7dfbdaa7..a6f6d1f3 100644 --- a/serverless/workers/github-integration.mdx +++ b/serverless/workers/github-integration.mdx @@ -88,8 +88,21 @@ You can monitor your build status in the **Builds** tab of your endpoint detail | Completed | Runpod completed the build and upload. | | Failed | Something went wrong (check build logs). | + +## Updating your endpoint + +When you make changes to your GitHub repository, they won't automatically be pushed to your endpoint. To trigger an update for the workers on your endpoint, create a new release for the GitHub repository. + +For detailed instructions on creating releases, see the [GitHub documentation](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository). + ## Roll back to a previous build + + +GitHub rollbacks are currently in beta. [Join our Discord](https://discord.gg/runpod) if you'd like to provide feedback. + + + Roll back your endpoint to any previous build directly from the Runpod console. This restores your endpoint to an earlier version without waiting for a new GitHub release. ### Requirements @@ -138,12 +151,6 @@ When you roll back an endpoint: - Your endpoint remains on the rolled-back version until you deploy a new release from GitHub. - When you push a new commit and create a release, the new build automatically becomes the active version and supersedes the rollback. -## Updating your endpoint - -When you make changes to your GitHub repository, they won't automatically be pushed to your endpoint. To trigger an update for the workers on your endpoint, create a new release for the GitHub repository. - -For detailed instructions on creating releases, see the [GitHub documentation](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository). - ## Managing multiple environments GitHub integration enables streamlined development workflows by supporting multiple environments: From 855636b08df2d97965536ff31fbc53d554752bf6 Mon Sep 17 00:00:00 2001 From: Mo King Date: Thu, 4 Dec 2025 15:27:12 -0500 Subject: [PATCH 3/3] Remove note --- serverless/workers/github-integration.mdx | 6 ------ 1 file changed, 6 deletions(-) diff --git a/serverless/workers/github-integration.mdx b/serverless/workers/github-integration.mdx index a6f6d1f3..f89c2780 100644 --- a/serverless/workers/github-integration.mdx +++ b/serverless/workers/github-integration.mdx @@ -136,12 +136,6 @@ Review the confirmation modal and click **Confirm** to proceed with the rollback After confirming, your endpoint rolls back to the selected build. A banner appears at the top of the endpoint page indicating the endpoint is on a rolled-back version. - - -The rollback banner only appears when your endpoint is actively using a previous build version. Once you push a new commit and create a release, the banner disappears and your endpoint uses the new build. - - - ### Understanding rollback behavior When you roll back an endpoint: