Add cooldown mechanism for npm package publishing #287
Conversation
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
Implements a cooldown period to prevent too-frequent npm package publishes: - Adds cooldown check before publishing (24-hour minimum between publishes) - Fails gracefully with clear message showing time remaining if cooldown active - Updates timestamp after successful publish using GitHub repository variables - Uses LAST_NPM_PUBLISH_TIME variable to track last publish time The workflow will now: 1. Check if 24 hours have passed since last publish 2. Display time remaining if cooldown still active 3. Proceed with normal publish if cooldown expired 4. Update timestamp after successful publish
Cordobo
commented
Nov 29, 2025
Cordobo
commented
Nov 29, 2025
The actions/setup-node action already handles npm authentication automatically when registry-url is configured, so the explicit NODE_AUTH_TOKEN environment variable is redundant.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implements a cooldown period to prevent too-frequent npm package publishes:
The workflow will now: