# Is Radicle meant to be updated?

**URL:** https://discourse.roots.io/t/is-radicle-meant-to-be-updated/27807
**Category:** radicle
**Created:** 2024-07-23T18:43:01Z
**Posts:** 3

## Post 1 by @alexbohariuc — 2024-07-23T18:43:02Z

Hey,

I was just wondering if Radicle was meant to be updated - since a new version or a pull would basically overwrite the files.

If one wants to keep it updated would have to cherry pick PRs? Or is there another way?

Thanks!

---

## Post 2 by @ben — 2024-07-24T15:28:53Z

Radicle is a boilerplate/starting point — any changes made to Radicle itself since you start a project with Radicle would need to be manually pulled in

I’d recommend getting Renovate/dependabot enabled on your repos for dependency updates, and occasionally manually merging in changes from upstream Radicle if they make sense to adopt

> [@alexbohariuc](#):
>
> If one wants to keep it updated would have to cherry pick PRs?

That could work, depending on how much customization you’ve done on your own to your Radicle site

> [@alexbohariuc](#):
>
> Or is there another way?

Copy and pasting :sweat_smile: For example, in Radicle v1.4.0 there was an update made to `theme.json`:

[https://github.com/roots/radicle/pull/167/files](https://github.com/roots/radicle/pull/167/files)

This is a quick change that can be copied and pasted into the relevant file

Occasionally there will be bigger changes, like [upgrading to Acorn v4](https://github.com/roots/radicle/pull/136/files), and you could also reference our other resources for changes like that ([Acorn upgrade guide](https://roots.io/acorn/docs/upgrading-acorn/))

---

## Post 3 by @alexbohariuc — 2024-07-26T17:17:20Z

Makes sense - I usually keep the packages updated - Bud, Acorn, et caetera.

Thanks for the answer!