What changed, and why it matters
This commit adds a standard GitHub Actions workflow that automatically creates a release when a version tag like '1.0' is pushed. It is purely a CI/CD automation change and does not modify application code, user-facing behavior, or security controls.
No security action required. Optionally review workflow permissions in repository settings to ensure GITHUB_TOKEN has only required write access.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The new .github/workflows/release.yml triggers on tags matching [0-9]+.[0-9]+ and uses the official actions/create-release@v1 action with the built-in GITHUB_TOKEN to publish a GitHub release. There are no code changes to the LNbits Paywall extension itself.
Changed components
.github/workflows/release.ymlInspect captured patch +19 / −0
### .github/workflows/release.yml
@@ -0,0 +1,19 @@
+name: release github version
+on:
+ push:
+ tags:
+ - "[0-9]+.[0-9]+"
+jobs:
+ build:
+ runs-on: ubuntu-latest
+ steps:
+ - name: Create GitHub Release
+ id: create_release
+ uses: actions/create-release@v1
+ env:
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+ with:
+ tag_name: ${{ github.ref }}
+ release_name: ${{ github.ref }}
+ draft: false
+ prerelease: falseWhy this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.