Skip to content

ci: scheduled check that latest GitHub release is published on npm #4266

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mfazekas merged 1 commit into from
Jul 22, 2026
+33 −0
Merged

ci: scheduled check that latest GitHub release is published on npm #4266

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions .github/workflows/check-npm-publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
name: Check NPM Publish
on:
schedule:
- cron: '30 6 * * *'
workflow_dispatch:
jobs:
check:
runs-on: ubuntu-latest
permissions:
contents: read
issues: write
steps:
- name: Verify latest GitHub release is on npm
env:
GH_TOKEN: ${{ github.token }}
run: |
tag=$(gh api "repos/$GITHUB_REPOSITORY/releases/latest" --jq .tag_name)
version=${tag#v}
if npm view "@rnmapbox/maps@$version" version > /dev/null 2>&1; then
echo "npm has @rnmapbox/maps@$version"
exit 0
fi
echo "::error::Release $tag exists on GitHub but @rnmapbox/maps@$version is not on npm"
title="npm publish missing for $tag"
existing=$(gh issue list --repo "$GITHUB_REPOSITORY" --state open --search "\"$title\" in:title" --json number --jq '.[0].number')
if [ -n "$existing" ]; then
echo "Issue #$existing already open"
else
gh issue create --repo "$GITHUB_REPOSITORY" \
--title "$title" \
--body "The latest GitHub release [\`$tag\`](${{ github.server_url }}/$GITHUB_REPOSITORY/releases/tag/$tag) is not published on npm (\`npm view @rnmapbox/maps@$version\` finds nothing). The publish workflow may have failed or never run. Detected by the scheduled Check NPM Publish workflow."
fi
exit 1
Loading