API not working for v0.6.500

[asukakimya]

16.32 npm error 404 '@hcengineering/ui@https://npm.pkg.github.com/download/@hcengineering/ui/0.6.500/f66966e800e4586d3899a0c31f855e836d1fcae8' is not in this registry.

:(

I use the v0.6.500 version but not working now

[ArtyomSavchenko]

Hi @asukakimya
Are you running the platform from sources?
Is this an error when building the application or is this error returned by the API?

[asukakimya]

Hi @ArtyomSavchenko ,

I’m currently experiencing a build issue on the API side of my project due to missing library dependencies. My project was originally built using version v0.6.500 of your packages, and while the main libraries are still available and functional, it appears that the /ui subpackage for version v0.6.500 has been removed or is no longer accessible.

Because of this missing subpackage, I’m now encountering errors during the build process specifically related to the UI library. The main dependencies themselves are fine — only the /ui portion of the v0.6.500 release seems to be affected.

Could you please confirm whether the @huly/.../ui@0.6.500 package was deprecated or removed, and if so, provide guidance on the correct version or migration path to resolve this issue?

Thank you in advance for your help and clarification.

my package.json:
{
"name": "fastify-huly-api",
"version": "0.2.0",
"type": "module",
"main": "src/index.js",
"scripts": {
"dev": "nodemon --watch src --exec "node --env-file .env src/index.js"",
"start": "node src/index.js"
},
"dependencies": {
"@fastify/autoload": "^5.10.0",
"@fastify/cors": "^8.4.0",
"@fastify/env": "^4.4.0",
"@fastify/sensible": "^5.6.0",
"@hcengineering/api-client": "0.6.500",
"@hcengineering/contact": "0.6.500",
"@hcengineering/core": "0.6.500",
"@hcengineering/task": "0.6.500",
"@hcengineering/tracker": "0.6.500",
"@hcengineering/tags": "0.6.500",
"@hcengineering/document": "0.6.500",
"@hcengineering/rank": "0.6.500",
"fastify": "^4.28.0",
"ws": "^8.18.3"
},
"devDependencies": {
"nodemon": "^3.0.3"
}
}

error:
'@hcengineering/ui@https://npm.pkg.github.com/download/@hcengineering/ui/0.6.500/f66966e800e4586d3899a0c31f855e836d1fcae8' is not in this registry.

[ArtyomSavchenko]

Hi @asukakimya
In the current versioning scheme, package versions do not match the build version
So I think for the v0.6.500 the following dependencies should be used:

"@hcengineering/api-client": "^0.6.0",
"@hcengineering/contact": "^0.6.24",
"@hcengineering/core": "^0.6.32",
"@hcengineering/task": "^0.6.20",
"@hcengineering/tracker": "^0.6.24",
"@hcengineering/tags": "^0.6.16",
"@hcengineering/document": "^0.6.0",
"@hcengineering/rank": "^0.6.4"

[asukakimya]

Hi @ArtyomSavchenko

Thanks for the quick reply and for the suggested dependency list.

A few follow-up questions so I can resolve this correctly:

1. If I replace my exact 0.6.500 pins with the caret ranges you suggested (for example, "@hcengineering/core": "^0.6.32"), will that change break an existing build that was previously working with 0.6.500? In other words — are there breaking or incompatible changes between the 0.6.500 build layout and the ^0.6.x package versions you listed?

2. Do the platform API and the huly/@hcengineering/* packages need to have exactly matching version numbers (e.g., both 0.6.500) to work together, or is it safe to mix (API at one semantic version and packages at another ^0.6.x) as long as they are in the same major version? Please clarify the compatibility rules.

3. The specific error I’m getting is a 404 from the registry for the UI package:

npm ERR! 404 '@hcengineering/ui@[https://npm.pkg.github.com/download/@hcengineering/ui/0.6.500/...]' is not in this registry.

Can you confirm whether @hcengineering/ui@0.6.500 was intentionally removed, renamed, or moved to a different registry/path? If it was removed, is there a recommended replacement package or migration path I should follow to restore a working build?

For reference, my package.json currently pins the following packages to 0.6.500:

"@hcengineering/api-client": "0.6.500",
"@hcengineering/contact": "0.6.500",
"@hcengineering/core": "0.6.500",
...

If there’s a short recommended set of exact versions (not ranges) that reproduce the v0.6.500 build layout, could you please share them? Alternatively, if re-publishing or restoring the missing ui package is possible, that would also solve my issue.

Thanks in advance for the clarification — I appreciate any concrete migration or version pins you can provide so I can get my build back to a known-good state.