# Error occurs when attempting to upgrade code repository

**URL:** <https://community.palantir.com/t/error-occurs-when-attempting-to-upgrade-code-repository/7443>\
**Category:** Ask the Community\
**Tags:** code-repositories, functions\
**Created:** [November 3, 2026, 8:36am UTC](https://community.palantir.com/t/error-occurs-when-attempting-to-upgrade-code-repository/7443 "2026-11-03T08:36:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidszy](https://avatars.discourse-cdn.com/v4/letter/d/53a042/32.png) [@davidszy](https://community.palantir.com/u/davidszy)\
**Post date:** [November 3, 2026, 8:36am UTC](https://community.palantir.com/t/error-occurs-when-attempting-to-upgrade-code-repository/7443/1 "2026-11-03T08:36:09Z")

</div>

Hi everyone!

I opened up my code repository today and encountered the following error:

 ![image](https://canada1.discourse-cdn.com/palantir/original/2X/1/1ba852aeb26727f909aa0363ddb119285d200a10.png)

I’m met with another error when clicking ‘Upgrade’ at the top right of my code repo:

 ![image](https://canada1.discourse-cdn.com/palantir/original/2X/6/62826239fd89ac97f0d783d13c3782e0894b14e1.png)

The error message is kind of unhelpful. What gives?

---

<div class="post-metadata">

**Author:** ![sriniN](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/srinin/32/8526_2.png) [@sriniN](https://community.palantir.com/u/sriniN)\
**Post date:** [November 3, 2026, 3:38pm UTC](https://community.palantir.com/t/error-occurs-when-attempting-to-upgrade-code-repository/7443/3 "2026-11-03T15:38:50Z")

</div>

@davidszy

the first error is the real one. your repo pins node 22.21.1 and the artifact proxy no longer serves that version (the 403 on nodeSetup), so the repo has to be upgraded to pull a newer node. someone hit the same thing yesterday with a 403 on a different node version, upgrade + merge fixed it: https://community.palantir.com/t/7437

for the “Invalid Argument” on Upgrade, a few things to check:

1. look at the pull requests tab first. upgrades come as a PR from a separate branch into your default branch, so if one is already open, merge that one instead of clicking Upgrade again
2. switch to your default branch (master/main) before clicking Upgrade, the upgrade PR targets the default branch
3. make sure you’re owner/editor on the repo, merging into a protected branch needs that
4. if there’s an old upgrade PR that someone committed to, or it overwrites template files you edited, it won’t merge cleanly. close it and run Upgrade again

after the merge, refresh, and if you have a lockfile regenerate it, the person in the other thread had to do that too before checks went green.