Skip to content

Publish packages 🚀 #377

Publish packages 🚀

Publish packages 🚀 #377

name: Changelog Reminder
on:
pull_request:
types: [opened, synchronize, reopened, ready_for_review]
paths:
- 'packages/clips/src/**'
- 'packages/clips/package.json'
- 'packages/clips-react/src/**'
- 'packages/clips-react/package.json'
- 'packages/cli/src/**'
- 'packages/cli/package.json'
- '!*.test.*'
- '!*.md'
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
jobs:
remind:
name: Changeset Reminder
runs-on: ubuntu-latest
timeout-minutes: 5
if: ${{ !github.event.pull_request.draft && !startsWith(github.head_ref, 'changeset-release/') }}
steps:
- uses: actions/checkout@v4
- uses: mskelton/changelog-reminder-action@v3
with:
changelogRegex: "\\.changeset"
message: >
We detected some changes in public packages, and there are no updates in the `.changeset` directory.
If the changes are user-facing and should cause a version bump, run `pnpm changeset` to track your changes and include them in the next release CHANGELOG.
If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.