chore: remove nightly schedule from resource fetcher publish workflows - #1192
Merged
Conversation
Resource fetcher packages rarely change, so daily nightly publishes bloat npm with effectively identical versions. Drop the cron trigger and keep workflow_dispatch (with latest-build toggle) so we can still publish manually when needed.
barhanc
approved these changes
May 27, 2026
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
2 participants
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
The bare-resource-fetcher and expo-resource-fetcher packages rarely change, but the publish workflows ran on a nightly cron, flooding npm with effectively identical versions. Drop the
scheduletrigger from both workflows; keepworkflow_dispatch(with thelatest-buildtoggle) so we can still publish manually — including a nightly tag — when needed.Introduces a breaking change?
Type of change
Tested on
Testing instructions
CI-only change. Verify in the Actions tab that "NPM publish bare-resource-fetcher" and "NPM publish expo-resource-fetcher" no longer list a scheduled trigger but can still be dispatched manually.
Screenshots
Related issues
Closes #1167
Checklist
Additional notes