CI/CD

[alvarosabu]

The idea of this discussion is to figure out a proper CI/CD and release management before going public

Current

Atm, I'm doing all the bumping of versions, changelogs, and releases manually, which is not maintainable in time and slows done quick delivery.

The current workflow is:

1. Change is made on @tresjs/core.
2. Commit: feat(core): whatever
3. PR and merge to main
4. Release branch is created release/core-1.x.0 since a feat with no breaking changes is a minor release
5. Version is bumped on core's package.json
6. Versions of core are updated manuallty on each of the other packages ` "@tresjs/core": "workspace:^1.x.0",
7. Changelog is created with conventional-changelog -p angular -i CHANGELOG.md -s ⚠️ The problem with this one is that always add all of the commits since the beginning, so I have to manually delete all the ones that are not going to release
8. Changes are commited and push
9. PR is checked and merged into main
10. pnpm build:ci && git status && pnpm publish:pkgs
11. git tag is created manually like this git tag -a @tresjs/core@1.6.3 -m "Release @tresjs/core@1.6.3"

Solution

The monorepo will be divided in several repos here #150, when that's done we can

• Apply release-it to core
• Apply release-it to cientos

[alvarosabu]

https://github.com/unocss/unocss/blob/main/package.json#L17