# Dependency Pinning

**URL:** https://forum.heroiclabs.com/t/dependency-pinning/4858
**Category:** Runtime Framework
**Tags:** server-framework
**Created:** [January 10, 2024, 10:21am UTC](https://forum.heroiclabs.com/t/dependency-pinning/4858 "2024-01-10T10:21:22Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![BernardoSantos](https://avatars.discourse-cdn.com/v4/letter/b/a87d85/32.png) [@BernardoSantos](https://forum.heroiclabs.com/u/BernardoSantos)
#### Post date: [January 10, 2024, 10:21am UTC](https://forum.heroiclabs.com/t/dependency-pinning/4858/1 "2024-01-10T10:21:22Z")

</div>

Hey!

Whenever I try to upgrade packages/nakama version and so on.

I keep getting errors regarding pragma package.

```auto
plugin.Open(\"/nakama/data/modules/backend\"): plugin was built with a different version of package google.golang.org/protobuf/internal/pragma

```

What is the fix?

I updated the nakama commons versions, which updates the protobuf version.  
After downgrading the protobuf it worked, just doesnt seem intuitive.

---

<div class="post-metadata">

### Author: ![sesposito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/sesposito/32/2594_2.png) [@sesposito](https://forum.heroiclabs.com/u/sesposito)
#### Post date: [January 10, 2024, 11:52am UTC](https://forum.heroiclabs.com/t/dependency-pinning/4858/2 "2024-01-10T11:52:40Z")

</div>

Unfortunately this is a limitation in how Go plugins work and the tooling around it, there’s not much we can do to prevent this, the dependencies (direct and indirect) in the plugin have to match the server’s.