Dependency Dashboard

[renovate]

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Config Migration Needed

• Select this checkbox to let Renovate create an automated Config Migration PR.

Warning

These dependencies are deprecated:

Datasource	Name	Replacement PR?
bun	@types/puppeteer

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update bun packages (major) (@types/chroma-js, puppeteer)

Detected dependencies

bun

package.json

• chroma-js ^3.0.0
• fast-deep-equal ^3.1.3
• svgson ^5.3.1
• events ^3.3.0
• @biomejs/biome 1.9.4
• @commitlint/config-conventional ^19.5.0
• @softarc/sheriff-core ^0.18.0
• @types/chroma-js ^2.4.4
• @types/puppeteer ^7.0.0
• axios ^1.7.2
• bun-types ^1.1.20
• changelogen ^0.5.7
• commitlint ^19.5.0
• esbuild ^0.24.0
• husky ^9.1.6
• lint-staged ^15.2.10
• markdownlint-cli ^0.44.0
• puppeteer ^23.0.0
• rimraf ^6.0.1
• svg-color-linter ^3.0.0
• svgo ^3.0.0
• typescript ^5.5.4
• vscode ^1.55.0

bun-version

.bun-version

• Bun 1.2.0

devcontainer

.devcontainer/devcontainer.json

• ghcr.io/michidk/devcontainers-features/bun 1

github-actions

.github/workflows/build.yml

• actions/checkout v4.2.2@11bd71901bbe5b1630ceea73d27597364c9af683
• oven-sh/setup-bun v2@4bc047ad259df6fc24a6c9b0f9a0cb08cf17fbe5

.github/workflows/close-stale-issues.yml

• actions/stale v9.1.0@5bef64f19d7facfb25b37b414482c7164d639639

.github/workflows/color-check.yml

• actions/checkout v4.2.2@11bd71901bbe5b1630ceea73d27597364c9af683

.github/workflows/icon-review.yml

• actions/checkout v4.2.2@11bd71901bbe5b1630ceea73d27597364c9af683
• actions/checkout v4.2.2@11bd71901bbe5b1630ceea73d27597364c9af683
• oven-sh/setup-bun v2@4bc047ad259df6fc24a6c9b0f9a0cb08cf17fbe5
• actions/github-script v7.0.1@60a0d83039c74a4aee543508d2ffcb1c3799cdea
• peter-evans/find-comment v3.1.0@3eae4d37986fb5a8592848f6a574fdf654e61f9e
• peter-evans/create-or-update-comment v4.0.0@71345be0265236311c031f5c7866368bd1eff043

.github/workflows/label.yml

• actions/labeler v5.0.0@8558fd74291d67161a8a78ce36a881fa63b766a9

.github/workflows/pr-closed.yml

• actions/github-script v7.0.1@60a0d83039c74a4aee543508d2ffcb1c3799cdea

.github/workflows/pr-title.yml

• actions/checkout v4.2.2@11bd71901bbe5b1630ceea73d27597364c9af683

.github/workflows/release.yml

• actions/create-github-app-token v1.11.1@c1a285145b9d317df6ced56c09f525b5c2b6f755
• actions/checkout v4.2.2@11bd71901bbe5b1630ceea73d27597364c9af683
• oven-sh/setup-bun v2@4bc047ad259df6fc24a6c9b0f9a0cb08cf17fbe5
• actions/attest-build-provenance v2.2.0@520d128f165991a6c774bcb264f323e3d70747f4
• HaaLeo/publish-vscode-extension v1.6.2@28e2d3f5817fccf23c1f219eb0cecc903132d1a2
• HaaLeo/publish-vscode-extension v1.6.2@28e2d3f5817fccf23c1f219eb0cecc903132d1a2

---

• Check this box to trigger a request for Renovate to run again on this repository

[okineadev]

why

[PKief]

@okineadev we get a PR once an update is available right? I don't see it so important to keep it pinned in our issues. In addition, it's only interesting for us maintainers not for everybody, right?

[PKief]

We can easily find this issue via our tags: 📦 dependencies Pull requests that update a dependency file

[okineadev]

ok

[lucas-labs]

Sorry about unpinning this and forgetting to leave a message explaining the reasons—my bad.

Before this issue was pinned, I recall another issue being pinned. It was one of the "add support for glob patterns" issues, which we can’t fix due to missing VS Code API support. That issue gets reported as duplicate quite frequently.

When I removed the pin for this one, my intention was to re-pin the "glob pattern" issue. However, I must have gotten distracted and never followed through 😅.

I think the issue number was 330, but I’m not entirely sure. (I’m not linking it with # here to avoid polluting the actual issue with reference events.)

I believe pinned issues should primarily help avoid duplicates or make it easier for users to find a common/repetitive issue and renovate creates PRs already, as Pkief mentioned.

[PKief]

@lucas-labs no worries, I've pinned #330 as well now. Hopefully it helps a little bit to avoid duplicates in the future. The dependency dashboard I'm not going to pin because it's not necessary due to the automated PRs.

I'm wondering if we can improve the duplicate detection in the future, for instance via some automated GitHub action workflows. But first I have to analyse some other projects to find out best practices. I also want to avoid many false positives in the end and avoid more confusion. So let's see what the future will bring.