Repository navigation
chore(ci): fix failing workflows, add dependabot, trim Actions usage - #8
Merged
Merged
Conversation
- Fix test script: the quoted glob `node --test 'test/*.test.mjs'` is only expanded by Node >= 21, so CI on Node 18/20 (and the auto-tag job) failed; use `node --test` auto-discovery instead. - auto-tag: serialize runs with a concurrency queue and skip/advance existing tags (back-to-back pushes raced for the same tag). - publish: trigger on release published / workflow_dispatch only; skip if the version is already on npm. - ci: add concurrency with cancel-in-progress. - Add dependabot (npm + github-actions, monthly, grouped minor/patch). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
node --test 'test/*.test.mjs'is only expanded by Node >= 21, so CI on Node 18/20 (and the auto-tag job) failed; usenode --testauto-discovery instead.Note: publishing to npm still needs credentials (no repo-level NPM_PUBLISH_TOKEN secret is visible / npm trusted publishing must be configured on npmjs.com).
🤖 Generated with Claude Code