ci: fix CI workflow startup failure and polish README - #79
Closed
BeiBaiNian wants to merge 1 commit into
Closed
Conversation
Member
|
done |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were made
1. Fix CI workflow startup failure (Apache org actions allowlist)
The CI workflow previously used two third-party actions that are not allowed in the
apacheorganization:supercharge/mongodb-github-action@1.7.0shogo82148/actions-goveralls@v1This caused the workflow to fail at startup ("Startup failure") before any test could run. Both have been removed:
mongo:4.4image viadocker run+rs.initiate(), no third-party action needed.actions/checkoutandactions/setup-goupgraded from v2 to v4 (official GitHub actions, allowlisted).2. Fix release workflow bugs
release-notes.md, but the next step referenced it viabody_path— the release would have failed on every tag push. Release notes are now written to the file.softprops/action-gh-release@v2(also not guaranteed on the Apache allowlist) with the built-inghCLI, which is idempotent (re-running safely updates the existing release).3. Polish README
apache/casbinmain repo style.apache/casbin-mongodb-adapterinstead of the oldcasbin/mongodb-adapterlinks.Checklist
actions/*used)release-notes.mdis actually generated before the release step