These workflows use APP_ID/APP_PRIVATE_KEY secrets that only exist on the upstream repo. Without a fork guard they fail on every push for every fork. merge-forward-skills already has the correct guard. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
34 lines
978 B
YAML
34 lines
978 B
YAML
name: Bump version
|
|
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
paths: ['src/**', 'container/**']
|
|
|
|
jobs:
|
|
bump-version:
|
|
if: github.repository == 'qwibitai/nanoclaw'
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/create-github-app-token@v1
|
|
id: app-token
|
|
with:
|
|
app-id: ${{ secrets.APP_ID }}
|
|
private-key: ${{ secrets.APP_PRIVATE_KEY }}
|
|
|
|
- uses: actions/checkout@v4
|
|
with:
|
|
token: ${{ steps.app-token.outputs.token }}
|
|
|
|
- name: Bump patch version
|
|
run: |
|
|
npm version patch --no-git-tag-version
|
|
git add package.json package-lock.json
|
|
git diff --cached --quiet && exit 0
|
|
git config user.name "github-actions[bot]"
|
|
git config user.email "github-actions[bot]@users.noreply.github.com"
|
|
VERSION=$(node -p "require('./package.json').version")
|
|
git commit -m "chore: bump version to $VERSION"
|
|
git pull --rebase
|
|
git push
|