TypeScript v2 Functions: workspace nodeSetup gets 403 downloading Node 24.16.0, but CI succeeds

I’m using a Developer Tier account with a TypeScript v2 Functions repository and the local Ontology SDK.

Branch CI succeeds, but Functions diagnostics and previews in the Code Workspace fail before compilation during Node setup.

Task: :typescript-functions:nodeSetup

Could not resolve org.nodejs:node:24.16.0

Artifact path:

contents/release/files/node/v24.16.0/node-v24.16.0-linux-x64.tar.gz

Request method: HEAD

Response: 403 Forbidden

The request is routed through Foundry’s artifact proxy. I’ve omitted the internal hostname and repository identifiers.

\### Configuration

\`gradle.properties\` contains:

properties

nodeInstallationVersion = 24.16.0

### What I’ve checked

- Restarted the affected workspace; the same failure persists.

- Confirmed Owner access to the repository. I understand this does not establish access to every backing artifact repository.

- Libraries settings lists the Functions TypeScript OSDK asset bundle and repository proxy.

- Opening the repository proxy displays “Restricted resource.” I’m unsure whether that is expected or related.

- Have not changed the Node version, reordered backing repositories or modified permissions.

CI reports success, but I have not independently verified the new unit-test results. Local tests cannot run because workspace dependency setup is blocked.

### Questions

1. Is Node 24.16.0 expected to be available through the standard Developer Tier Functions artifact configuration?

2. What is the supported way to investigate workspace artifact resolution returning 403 while branch CI succeeds?

3. Is the “Restricted resource” page expected for the Functions repository proxy, or does it indicate an access/configuration issue?

You need to upgrade your code repository to get the latest versions of the packages available.

On Palantir extension if you are in VS Code, or top right if you are in Code Repository, you should see an “upgrade” option.
This will open a pull request on your repository (you can access it at the top of the screen).

Merge this PR, refresh the page and everything should work again :slight_smile:

Thank you! The repository upgrade resolved the Node artifact download issue. After regenerating the stale dependency lockfile, diagnostics and tests are passing.