You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is one Automated Version Bump action found Github Action. Using this can enable automated checking based on the commit messages.
By applying this process the git commit message become very important to indicate if the version is major or minor release.
Workflow
Based on the commit messages, increment the version from the latest release.
If the string "BREAKING CHANGE" or "major" is found anywhere in any of the commit messages or descriptions the major version will be incremented.
If a commit message begins with the string "feat" or includes "minor" then the minor version will be increased.
This works for most common commit metadata for feature additions: "feat: new API" and "feature: new API".
All other changes will increment the patch version.
Push the bumped npm version in package.json back into the repo.
Push a tag for the new version back into the repo.
The above Automated Version Bump have shown the disadvantage of monorepo, this is dangerous especially when the changes is focused at one component. The version bump is taking place in overall project. This is undesirable. This brings the split of repository to have multiple plugins as respective repo. The one required work required is also a nest library for extractor plugin. This will ensure how the Task Scheduler will able to call the extractor to activate certain plugins .
This public API facing between the taskscheduler and the extractor should be finalized before starting the next development .
The public API facing between the taskscheduler and the AIFactory should also be finalized but this can be push to lower priority as the requirement of collecting the data have to be prioritized first.
Using the github action , the version bump workflow should be created .
Create Wiki to define how the Version works for this project
Define how the github action will automate the process of version bumping
The text was updated successfully, but these errors were encountered: