Codecov Report

Merging #24 (9670dcd) into master (b6525cb) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #24   +/-   ##
=========================================
  Coverage     59.64%   59.64%           
  Complexity       93       93           
=========================================
  Files            16       16           
  Lines           394      394           
  Branches         39       39           
=========================================
  Hits            235      235           
  Misses          131      131           
  Partials         28       28           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b6525cb...9670dcd. Read the comment docs.

@fangzhengjin please review.

@wy10cheng @daiyueliang plz review.

Sorry,Could you also update casbin-spring-boot-starter.jar in maven repository ?
Thank you

Sorry,Could you also update casbin-spring-boot-starter.jar in maven repository ?
Thank you

I do not understand what you mean.

Sorry,Could you also update casbin-spring-boot-starter.jar in maven repository ?
Thank you

I do not understand what you mean.

https://mvnrepository.com/artifact/org.casbin/casbin-spring-boot-starter
⇧Sorry,here don't need update?

Sorry,Could you also update casbin-spring-boot-starter.jar in maven repository ?
Thank you

I do not understand what you mean.

https://mvnrepository.com/artifact/org.casbin/casbin-spring-boot-starter
⇧Sorry,here don't need update?

Need to update, but does this have anything to do with the issue we are discussing now?

Should we consider checking the existing database and adding the id field to allow users of the old version to upgrade without hindrance?
Or do we issue an announcement on the impact of the upgrade?

@shy1st whether do you think we need it?

Should we consider checking the existing database and adding the id field to allow users of the old version to upgrade without hindrance?
Or do we issue an announcement on the impact of the upgrade?

@shy1st whether do you think we need it?

I think we don't need it. We can issue an announcement on the impact of the upgrade.

@shy1st plz make a Maven & GitHub Release (or we can use your new semantic-release feature)

Excuse me,could you tell me what command you usually use to release the version to the maven repository for this project? @fangzhengjin

Excuse me,could you tell me what command you usually use to release the version to the maven repository for this project? @fangzhengjin

Modify the version_code in the gradle.properties file and tag it. After Travis is built, it will be published to bintray, and then you need to log in to bintray to synchronize to MavenCenter.

Excuse me,could you tell me what command you usually use to release the version to the maven repository for this project? @fangzhengjin

Modify the version_code in the gradle.properties file and tag it. After Travis is built, it will be published to bintray, and then you need to log in to bintray to synchronize to MavenCenter.

Thanks.

Try not to mark when you have not modified the version_code, because it may overwrite the build of the previous version of bintray.

@shy1st plz use English. Actually I don't know why the quoted content becomes Chinese :)

Excuse me,could you tell me what command you usually use to release the version to the maven repository for this project? @fangzhengjin

Modify the version_code in the gradle.properties file and tag it. After Travis is built, it will be published to bintray, and then you need to log in to bintray to synchronize to MavenCenter.

Thanks.

@shy1st plz use English. Actually I don't know why the quoted content becomes Chinese :)

Sorry, it was a mistake.