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
The version specified in CMake config and the version released by GitHub Actions is not the same and can be really confusing for the clients. We can automate the versioning to coincide the CMake version with the GH version of casbin-cpp through another GitHub Action which should trigger on push to master branch.
The text was updated successfully, but these errors were encountered:
Good point. But I think it's maybe difficult to do that automatically. Because if we update cmake file atfer a new release, we will generate change in cmakelists.txt. And I can't find a plugin can do that thing. Maybe we can update cmake version with the release rule. This is a very tricky thing. @EmperorYP7
Description
The version specified in CMake config and the version released by GitHub Actions is not the same and can be really confusing for the clients. We can automate the versioning to coincide the CMake version with the GH version of casbin-cpp through another GitHub Action which should trigger on push to
master
branch.The text was updated successfully, but these errors were encountered: