ljharb / ljharb/safe-array-concat

Dependency Dashboard

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Description

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/ljharb/safe-array-concat).

## Pending Approval

The following branches are pending approval. To create them, click on a checkbox below.

- [ ] [Deps] Update Update `evalmd` to ^0.0.22
- [ ] [Deps] Update Update `eslint` to v10
- [ ] [Deps] Update Update `nyc` to v18
- [ ] 🔐 **Create all pending approval PRs at once** 🔐

## Detected Dependencies

github-actions (6)

.github/workflows/node-aught.yml (1)

- `ljharb/actions main`

.github/workflows/node-pretest.yml (1)

- `ljharb/actions main`

.github/workflows/node-tens.yml (1)

- `ljharb/actions main`

.github/workflows/node-twenties.yml (1)

- `ljharb/actions main`

.github/workflows/rebase.yml (1)

- `ljharb/actions main`

.github/workflows/require-allow-edits.yml (1)

- `ljharb/require-allow-edits main`

npm (1)

package.json (24)

- `call-bind ^1.0.9`
- `call-bound ^1.0.4`
- `get-intrinsic ^1.3.0`
- `has-symbols ^1.1.0`
- `isarray ^2.0.5`
- `@arethetypeswrong/cli ^0.18.2`
- `@ljharb/eslint-config ^22.2.2`
- `@ljharb/tsconfig ^0.3.2`
- `@types/call-bind ^1.0.5`
- `@types/get-intrinsic ^1.2.3`
- `@types/isarray ^2.0.3`
- `@types/tape ^5.8.1`
- `auto-changelog ^2.5.0`
- `encoding ^0.1.13`
- `eslint ^8.57.1` → [Updates: `^10.0.0`]
- `evalmd ^0.0.19` → [Updates: `^0.0.22`]
- `in-publish ^2.0.1`
- `mock-property ^1.1.0`
- `npmignore ^0.3.5`
- `nyc ^10.3.2` → [Updates: `^18.0.0`]
- `safe-publish-latest ^2.0.0`
- `set-function-length ^1.2.2`
- `tape ^5.9.0`
- `node >=0.4`

---

- [ ] Check this box to trigger a request for Renovate to run again on this repository

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Dependency Dashboard documentation linked in the issue, then review package.json and the listed .github/workflows files. Check the pending evalmd, eslint, and nyc updates and the GitHub Actions dependencies before deciding which approvals are appropriate. Done means the selected updates are approved and their resulting changes are validated.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, javascript
Domain
devops, tooling
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.