Getting corrupted tarball data for @umbraco-cms/backoffice v15.1.1

[JoseMarcenaro]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.1.1

Bug summary

I am building a package.json with a reference to the latest backoffice version (15.1.1)
On my local machine, npm i runs without incidents
On an Azure Devops pipeline, the same command aborts with this error:

tarball data for @umbraco-cms/backoffice@https://registry.npmjs.org/@umbraco-cms/backoffice/-/backoffice-15.1.1.tgz (sha512-Aoy/lFLXDxRIWYF5cM4YNTM7CRdSRbKE463271IXpvyLJUa0xg9pSdrKwsw+i0/YySDSnvXgwQ63WBKN3IJFtQ==) seems to be corrupted

Specifics

The default registry.npmjs.org is used - should I include a nuget.config to use a different registry?

Steps to reproduce

Include these dependencies in package.json

  "devDependencies": {
    "@hey-api/openapi-ts": "^0.57.1",
    "@umbraco-cms/backoffice": "^15.1.1",
    "typescript": "^5.7.2",
    "vite": "^5.4.11"
  }

and try to run npm i in an AzureDevops pipeline, i.e:

  - task: UseNode@1
    displayName: Use Node 20.11.0
    inputs:
      version: 20.11.0
  - script: npm i
    displayName: 'npm install dependencies'      
    workingDirectory: .\src\my-project

Expected result / actual result

No response

[github-actions]

Hi there @JoseMarcenaro!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[JoseMarcenaro]

Ups. Looks like a difference in the sha512 integrity checksum with my package-lock.json.
Closing the issue for now.