ci: scheduled check that latest GitHub release is published on npm#4266
Merged
Conversation
Daily audit comparing the latest GitHub release against npm; opens an issue (deduped by title) when the release version is missing from the registry. Catches publish failures even when the publish workflow never ran, e.g. the v10.3.3/v10.3.4 EBADENGINE failures that went unnoticed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a scheduled workflow (daily, plus manual dispatch) that checks the latest GitHub release is actually published on npm. If
npm view @rnmapbox/maps@<version>finds nothing, it opens an issue (deduped by title, so repeated runs won't spam) and fails the run.Complements #4265: the
notify-failurejob there covers the case where the publish workflow runs and fails, this catches the whole class including the workflow never firing. Dry-run against the current state correctly detects that v10.3.4 is missing from npm.Checklist
CONTRIBUTING.mdyarn generatein the root folder/exampleapp./example)CI-only change; example app checklist items are not applicable.