Release commits of v1.3.0 and v1.4.0 do not belong to this repository

[clueleaf]

Releasing a commit outside of the original repository is a potential security risk.

[bluesentinelsec]

Hello @clueleaf, thank you for reaching out regarding commits that do not appear to belong to this repository. We reviewed the project commit history in detail from all users and did not observe any indications of unauthorized commits. The warning is appearing because commit 4e74c04 (v1.3.0) is on a branch that diverged from main. These commits were not merged back into main in the correct sequence, resulting in the warning. While I observed the warning for tag v1.3.0 I did NOT observe the warning for tag v1.4.0. Regardless, we will continue to refine our release processes so that these warnings do not appear in the future. In the mean time, you can safely upgrade to our latest release v1.4.1 and the warning should go away.

Please reach out if you have subsequent questions or concerns, otherwise, we're marking the issue as resolved.

[clueleaf]

Thank you!