WIP: Feat/versioning

[cre8]

Update of this PR:

vitest usage: vitest was configured for workspace usage. This will generate a coverage report for all files (open todos: publish result file to codecoverage for better inspection. We need to set a token as a secret).

adding lint: to improve code quality lint was added. But for not it is outcomment during the ci since it would not pass ;)

optimized ci: I used veramos one as a reference. It will build and test the code. It will also publish the code to NPM when it is on one of the specific branches

• if its on main, it will publish the latest version and also with a new version number based on the tags. It will also generate a release
• if its on next, it will publish the latest version under the next tag, but will not give it a new version number
• similar to next, but it will publish it with the unstable tag.

Signed-off-by: Mirko Mollik [email protected]

[lukasjhan]

Looks good to me :)
Is it ready to merge?

[cre8]

@lukasjhan not yet

[cre8]

@lukasjhan since I am not getting the results I want with lerna, I will try to migrate to NX which seems to be more up to date how to handle monorepos.

[lukasjhan]

@cre8 The direction of change seems to be good, but what part is not working well?

[cre8]

@cre8 The direction of change seems to be good, but what part is not working well?

The continuous deployment is not working. Lerna has the call to generate the changelog and the updated version in the package jsons. But I found no good way to push these changes to the GitHub branch inside the GitHub action. I also found no documentation on the Lerna website.

Three options:

• we are doing the release manually in the short run
• we are checking how other projects using Lerna in their cicd have solved it
• we switch to other tools like nx where are plugins to publish

I already tested the switch to nx and it was done in 10 minutes.

I will evaluate all three options today so we merge this PR successful

[lukasjhan]

I'll put sd-jwt-vc PR after this :)

[cre8]

@lukasjhan I updated this entry so it can be reviewed again by you :)

[cre8]

I am not sure if the publish step will work at this point because I cannot check if we have all the required variables and secrets set

[lukasjhan]

Okay :) I'm reviewing right now.
The DCO check is failed. Do you want to bypass it?

[cre8]

I will fix the the DCO check by resigning in an hour.

[cre8]

@lukasjhan done, an hour is relative :D

[lukasjhan]

I assume that this changelog generated automatically, is it right?
It might be needed to fix manually as we discuss in #44. To 0.x

[cre8]

I think we should remove the generated one from this PR. As mentioned above, I don't know what's the best way to generate the changelog that should be part of the github repo. It should be relatively easy to use the release mechanism of github

[lukasjhan]

@cre8 I think we might need to reset all the tags in this repo when we deploy to @sd-jwt/*

[lukasjhan]

I guess release mechanism of github is easiest way :D.