Versions got dropped to the initial one

[morozovamv]

Hi! I've upgraded my project to nx@17.2.6 and after running version update on GitLab ci yarn exec nx run-many --all --target=version --skip-nx-cache it ran nx run ***:version for each of the app/library and dropped all versions to 0.1.0.
Normally that command would skip libs that didn't have any changes and it would upgrade version for example 39.9.1 -> 39.9.2.
Do you know why this could happen?

We use "@jscutlery/semver": "4.1.0".

[edbzn]

Hi @morozovamv, can you show me the semver config you are using?

[morozovamv]

Seems ok too

Just to give you more context, these are deps changes, maybe you notice something

[morozovamv]

More context: there is another issue with commitlint (conventional-changelog/commitlint#3820), I also made a workaround that was suggested in the issue. I'm not sure if that is related to my current issue.

[edbzn]

Not sure it's related actually. I'm investigating I'll keep you informed.

[morozovamv]

Seem to be fixed, steps I've done:

• deleted all wrong commits from git history (ex. "chore(**$**expereo-ui): Release version 0.0.2"; $-sign shouldn't be there)
• deleted all wrong tags (like **$**expereo-ui@0.0.2; $-sign shouldn't be there)
• moved our local tags to the latest commit
• changed config

As a result version was generated correctly on GitLab CI

I don't know at what point it got broken, hopefully future MR will be also fine.

[morozovamv]

I also noticed another issue with versions on the changelog.md, it was wrong since the beginning and after I've done the versions fix, it changed but it is still wrong. Could you point me, what can I check to fix it?
The issue is that in the changelog we track version updates. Previously after some dependency got an update, there was a message about it, but it had wrong dependency version ("dep ***" updated to version "0.1.0") - it was always 0.1.0. Now, after fix, instead of 0.1.0 there is a version of a parent dependency, not of the dependency itself. You can see it on the screenshot. Setup is done according to (https://github.com/jscutlery/semver?tab=readme-ov-file#tracking-dependencies)

[edbzn]

I think it's related to a known issue: #526

[morozovamv]

All clear, thank you for your help @edbzn!