[Client] cannot upgrade 2023.06-ext5 to 2023.06-ext8

Client
1

Hi, our project is upgrading from 2023.06-ext5 to 2023.06-ext8 but got an error during run npm i

image
image1163×652 74.2 KB

This is current and new changes from our package.json

image
image1765×510 83.6 KB

How can I upgrade project?

Thank you.

2

Look like peer version doesn’t match. Have you tried to increase version of utils to 5.8.1?

3

Not yet, I’m following version in GetA12
Look like utils 5.8.1 for 2024.06 and it not match with 2023.06 (as theory). But I will try

UPDATE

It throw another issue when upgrade utils to 5.8.1

image
image1205×571 77.6 KB

4

utils-localization 5.8.1 does not exist.

I think the only combination that you can try is:

utils-logging @ 5.8.1
utils-localization @ 5.7.0
utils-localization-react @ 5.7.0

However, I think the workflows-core library should not have declared a utils-logging version of ^5.8.1 in the first place.

I will ask the workflows dev team about it.

5

Thank @erik-radiant-gorge,
I have a call with a12 team and he supports me same as you. It work now at my project
Here is our version:

"@com.mgmtp.a12.utils/utils-connector": "6.0.8",
"@com.mgmtp.a12.utils/utils-localization": "5.7.0",
"@com.mgmtp.a12.utils/utils-localization-react": "5.7.0",
"@com.mgmtp.a12.utils/utils-logging": "5.8.1",

Look like releases-overview do not match for ext8.

6

Hi @anh-round-summit,

you are right there is a mistake in the utils versions in the releases overview for 2023.06. This is caused by a recent restructuring of utils. I am sincerely sorry about this.
I have created A12-16473 to have this fixed. I will update this thread, once it is done.

Best,
Denise

7

Thank you @denise-narrow-token

For another project, here is our package version for 2023.06-ext8. You can follow it.

    "@com.mgmtp.a12.base/base-model-api": "27.1.0",
    "@com.mgmtp.a12.client/client-core": "14.6.3",
    "@com.mgmtp.a12.dataservices/dataservices-access": "36.3.9",
    "@com.mgmtp.a12.formengine/formengine-core": "36.7.4",
    "@com.mgmtp.a12.kernel/kernel-core-runtime-api-ts": "28.5.3",
    "@com.mgmtp.a12.kernel/kernel-md-facade": "28.5.3",
    "@com.mgmtp.a12.overviewengine/overviewengine-core": "36.5.1",
    "@com.mgmtp.a12.uaa/uaa-authentication-client": "7.5.3",
    "@com.mgmtp.a12.utils/utils-connector": "6.0.8",
    "@com.mgmtp.a12.utils/utils-localization": "5.7.0",
    "@com.mgmtp.a12.utils/utils-localization-react": "5.7.0",
    "@com.mgmtp.a12.utils/utils-logging": "5.8.1",
    "@com.mgmtp.a12.widgets/widgets-core": "36.6.0",
    "@com.mgmtp.a12.workflows/workflows-access": "10.6.9",
    "@com.mgmtp.a12.workflows/workflows-core": "10.6.9"
8

Thanks for sharing this.

9

Hi @anh-round-summit,

upon further investigation, it turned out that the release table is correct, but workflows used the wrong minimum compatible versions for utils-logging & -collections in their peer dependencies (5.8.1 instead of 5.7.0).

They have fixed this in workflows version 10.6.10, so you can use this patch in your project with utils-logging 5.7.0 if you want. However, there are no significant functional differences between utils-logging versions 5.7.0 and 5.8.1, so you can also keep your versions as you have them right now.

Best,
Denise