Repository navigation
Remove duplicate CI runs and cache dependency downloads - #22
Merged
Merged
Conversation
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
This was referenced Nov 12, 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
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.
Each release previously ran the suite four times: branch push, pull request, main push, and release. Recent jobs took 34–37 seconds each, with 26–27 seconds testing, 3–4 seconds installing dependencies, and only 2 seconds publishing the release.
Run Tests on pull requests and manual dispatch only; retain the release workflow's tests on the merged commit before publishing. Cancel superseded PR test runs and enable npm download caching in both workflows, keyed by package.json because this repository does not track a lockfile.
This halves automatic suite executions for a typical one-commit PR/release from four to two. The duplicate runs previously overlapped, so wall-clock time will not necessarily halve. All regression tests remain, including the slow-storage history test. No userscript version bump or release is needed for workflow-only changes.
Validation: both workflows parse as YAML and git diff --check passes. The PR run validates the updated test workflow; the main release run should skip publication because v6.10.2 already exists.