> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encorekit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Routine updates

> How to update the Encore Web SDK and how its versioning works.

## Overview

The Encore Web SDK is a **public npm package**,
[`@encorekit/web-sdk`](https://www.npmjs.com/package/@encorekit/web-sdk). Updating is the
standard package-manager flow. No token or authenticated registry is required.

***

## Versioning policy

Encore follows [Semantic Versioning](https://semver.org):

| Version change | Example           | What it means                                            |
| :------------- | :---------------- | :------------------------------------------------------- |
| Patch          | `2.0.3` → `2.0.4` | Bug fixes. Safe to update.                               |
| Minor          | `2.0.x` → `2.1.0` | New features, backward compatible. Safe to update.       |
| Major          | `1.1.x` → `2.0.x` | Breaking changes. Follow that version's migration guide. |

Pin your dependency with the caret range `npm install` writes for you. Patch and minor
updates then arrive through a routine `npm update`, and a major version never lands
without you opting in.

<Note>
  Coming from `2.0.0` or earlier? The 2.x public API arrives in `2.0.1`, so that step is a
  migration whatever the version numbers suggest. See
  [Updating to 2.x](./updating-to-2-x) for the step-by-step guide.
</Note>

***

## Update via your package manager

<Tabs>
  <Tab title="npm">
    ```bash theme={null}
    npm update @encorekit/web-sdk
    ```
  </Tab>

  <Tab title="yarn">
    ```bash theme={null}
    yarn up @encorekit/web-sdk
    ```

    On yarn 1, use `yarn upgrade @encorekit/web-sdk`.
  </Tab>

  <Tab title="pnpm">
    ```bash theme={null}
    pnpm update @encorekit/web-sdk
    ```
  </Tab>

  <Tab title="Script tag (UMD)">
    Re-fetch `dist/umd/encore.min.js` at the version you pin to, or refresh the hosted CDN
    URL if you serve it from one.
  </Tab>
</Tabs>

<Note>
  To see what you resolved to and what is current, run `npm ls @encorekit/web-sdk` and
  `npm view @encorekit/web-sdk version`.
</Note>

***

## Verify the update

```javascript theme={null}
import Encore from '@encorekit/web-sdk';

console.log('Encore SDK version:', Encore.getVersion());
```

[`getVersion()`](/publishers/web/sdk-reference/configure) reports what shipped in the
bundle you are running, not what your lockfile intended. If it disagrees with `npm ls`,
you are serving a cached bundle rather than a failed install.

***

## Related

* [Updating to 2.x](./updating-to-2-x): the step-by-step migration guide.
* [`configure()`](/publishers/web/sdk-reference/configure): the `getVersion()` entry and the rest of the top-level API.

If you encounter issues after updating, reach out to [admin@encorekit.com](mailto:admin@encorekit.com).