What the developer wrote
Authored by daywalker90
CI: remove crate-bump workflow
it was not picking up usage and is not working as intended either
Changelog-None
What changed, and why it matters
This commit simply deletes an unused GitHub Actions workflow file that automated version bumps for Rust crates. There is no change to the actual Core Lightning software, no security fix, and no vulnerability introduced.
No security action required. Treat as routine CI maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The removed .github/workflows/crate-bump.yml was a manually-triggered CI workflow for bumping cln-plugin, cln-rpc, or cln-grpc crate versions using cargo-release and cargo-semver-checks. It ran with GITHUB_TOKEN and created pull requests. Removing it reduces CI surface but does not alter shipped code, dependencies, or runtime behavior.
Changed components
.github/workflows/crate-bump.ymlInspect captured patch +0 / −68
diff --git a/.github/workflows/crate-bump.yml b/.github/workflows/crate-bump.yml
deleted file mode 100644
index 418fe10f..00000000
--- a/.github/workflows/crate-bump.yml
+++ /dev/null
@@ -1,68 +0,0 @@
-name: Bump Rust 🦀 crate version
-
-on:
- workflow_dispatch:
- inputs:
- dist-location:
- description: 'Distribution location'
- type: choice
- options:
- - cln-plugin
- - cln-rpc
- - cln-grpc
- default: 'cln-plugin'
- required: true
-
-jobs:
- bump:
- runs-on: ubuntu-latest
- timeout-minutes: 60
- steps:
- - name: Checkout repository
- uses: actions/checkout@v4
-
- - name: Setup protoc
- uses: arduino/setup-protoc@v3
-
- - name: Setup rust
- uses: dtolnay/rust-toolchain@1.77
-
- - name: Install cargo binstall
- uses: cargo-bins/cargo-binstall@main
-
- - name: Install cargo-release and cargo-semver-checks
- run: |
- cargo binstall cargo-release --version 0.25.10
- cargo binstall cargo-semver-checks --version 0.36.0
-
- - name: Determine version
- id: determine-version
- run: |
- if cargo semver-checks -p ${{ github.event.inputs.dist-location }} --release-type patch; then
- echo "bump=patch" >> $GITHUB_OUTPUT
- elif cargo semver-checks -p ${{ github.event.inputs.dist-location }} --release-type minor; then
- echo "bump=minor" >> $GITHUB_OUTPUT
- elif cargo semver-checks -p ${{ github.event.inputs.dist-location }} --release-type major; then
- echo "bump=minor" >> $GITHUB_OUTPUT
- else
- echo "bump=unknown" >> $GITHUB_OUTPUT
- exit 1
- fi
-
- - name: Bump version
- run: |
- cargo release version -p ${{ github.event.inputs.dist-location }} ${{ steps.determine-version.outputs.bump }} --execute --no-confirm
-
- - name: Create Pull Request
- uses: peter-evans/create-pull-request@v7
- with:
- token: ${{ secrets.GITHUB_TOKEN }}
- commit-message: "${{ github.event.inputs.dist-location }}: Bump the ${{ steps.determine-version.outputs.bump }} version"
- title: "${{ github.event.inputs.dist-location }}: Bump the ${{ steps.determine-version.outputs.bump }} version"
- body: |
- Triggered manually with option: ${{ github.event.inputs.dist-location }}
- Version bump determined by `cargo semver-checks`
- branch: "${{ github.event.inputs.dist-location }}-version-bump"
- base: master
- labels: version-bump, automated
- delete-branch: true
Why 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.