> For the complete documentation index, see [llms.txt](https://voyager-docs.devdojo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://voyager-docs.devdojo.com/1.3/getting-started/upgrading.md).

# Upgrading

## Upgrading 1.2 to 1.3

{% hint style="info" %}
Please take a look at our [prerequisites](/1.3/getting-started/prerequisites.md) before upgrading!
{% endhint %}

### Update your Composer.json

To update to the latest version inside of your composer.json file make sure to update the version of Voyager inside the require declaration inside of your composer.json to:

`tcg/voyager": "1.3.*`

And then run `composer update`

### Changes to VoyagerAuth

The `VoyagerAuth` singleton was introduced in Voyager 1.2 and returned an instance of the guard.\
In Voyager 1.3 this singleton was renamed to `VoyagerGuard` and now returns the name of the guard as a string. Read more on custom guards [here](/1.3/customization/custom-guard.md)

## Update Configuration

The `voyager.php` configuration file had a few changes.

```
'user' => [
    'namespace' => null,
],
```

was removed. The user-model which will be used in the `voyager:admin` command is now determined based on the [guard](/1.3/customization/custom-guard.md).

### Troubleshooting

Be sure to ask us on our slack channel if you are experiencing any issues and we will try and assist. Thanks.


---

# 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:

```
GET https://voyager-docs.devdojo.com/1.3/getting-started/upgrading.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.