Deployments, Versions & Rollback
Every time you deploy, HeroMate creates a new version of your frontend. The active version is what your users see. Older versions stay available so you can roll back instantly if something breaks.
Where this lives
Deployment history, build logs, and rollback live under the Deployments sub-item (Frontend → Deployments, route /deployments) — distinct from the Frontend Overview page (site URL, preview, deploy button, ZIP download). Full deploy history + 1-click rollback is a Pro feature.
Deployment history
Open Frontend → Deployments in your project dashboard. The deployments list shows every build, newest first, with:
- Version number — increments on every deploy (
v1,v2,v3…) - Status —
active,ready,building, orfailed - Created at — when the deploy was triggered
- Size — total output size of the build
- File count — how many assets were produced
Click any version to see its build logs, file list, and the exact commit (if deployed from Git).
Build logs
If a deploy fails, open its logs to see what went wrong. Typical issues:
- Missing dependency in
package.json - Build command failed (
npm run buildexited with error) - Output directory not found (HeroMate expects
dist/,build/, orout/depending on the framework) - Environment variable required at build time but not set
- Build timed out or the output was rejected as too large
Recent build logs are retained per project so you can debug failed deploys.
Rollback
Broke production? One click gets you back.
Find the version
Go to Frontend → Deployments and find the last version you know was working.
Click Rollback
Click Rollback to this version next to it. Confirm the prompt.
Instant switch
The active version switches immediately. No rebuild, no waiting — the old build is already cached at the edge. Usually live within seconds.
Rollback is not destructive
Rolling back doesn't delete newer versions. You can roll forward again to any version at any time.
Compare versions
Each version exposes its size and file count, so you can spot when a build suddenly doubled in size or lost assets. A side-by-side diff view is on the roadmap.
Automatic health checks
After every deploy, HeroMate verifies the new version responds with a 200 status. If it returns a 500 (build artifacts missing, bad routing, etc.), the deploy is automatically retried. You don't need to intervene.
Deploys that stay broken after retries are marked failed and the previous active version keeps serving traffic.
Download source
From the Frontend Overview you can download the current build's source as a ZIP. Use it to recover code after a lost local copy, audit what was actually deployed, or pass it to a collaborator.
Limits
| Versions kept | A recent history of versions per project (older ones are garbage-collected) |
| Rollback window | Any version still stored in history |
| Build logs | Recent deploys are retained for debugging |
| Full history + rollback | Pro plan |
Older versions are automatically garbage-collected to keep your storage usage reasonable.