> For the complete documentation index, see [llms.txt](https://docs.xenoraa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xenoraa.com/xenoraa-release-notes/v10.0.8-secure-automated-production-deployments.md).

# v10.0.8 — Secure Automated Production Deployments

**Release date:** 14 August 2026

Xenoraa now deploys automatically when approved code is pushed to `main`. The release pipeline validates the Laravel application first, then deploys through a dedicated self-hosted GitHub Actions runner on the production server.

## Highlights

| Improvement                       | Benefit                                                                                    |
| --------------------------------- | ------------------------------------------------------------------------------------------ |
| Validated main-branch deployments | Production deployment happens only after required CI checks pass.                          |
| No inbound GitHub SSH             | GitHub-hosted runners no longer need port 22 access to the production server.              |
| Dedicated runner identity         | The runner uses the restricted `xenoraa-runner` system account rather than root.           |
| Health verification               | Each deployment checks `https://xenoraa.com/up` before GitHub marks the job successful.    |
| Sentry release tracking           | The deployed Git commit is written to `SENTRY_RELEASE` for traceability.                   |
| Legacy-key retirement             | Obsolete GitHub SSH secrets and legacy Manus/GitHub Actions public keys have been removed. |

## How Releases Work Now

1. Developers complete work on a feature branch or `develop`.
2. GitHub Actions validates the change with dependency installation, frontend build, PHP linting, database migrations, and Unit tests.
3. When approved changes are pushed to `main`, the `xenoraa-production` runner deploys the checked `main` branch locally.
4. Laravel caches are rebuilt, PHP-FPM and queue workers are refreshed, and the health endpoint is checked.
5. GitHub Actions reports the deployment result in the repository Actions tab.

## First Verified Deployment

The new pipeline successfully deployed release `c8c6da1` through GitHub Actions workflow run **#3, attempt #3**. Production health was confirmed after deployment.

## Important Notes for Developers

* Use `main` only for production-ready changes because every push triggers the deployment pipeline.
* Do not add SSH deployment secrets or direct GitHub Actions server-access keys back to the repository.
* The existing Feature test suite is visible in CI but is not yet a release gate because it needs test-data and redirect-behavior remediation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xenoraa.com/xenoraa-release-notes/v10.0.8-secure-automated-production-deployments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.