stackabletech / stackabletech/crddocs
Dependency Dashboard
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
[!NOTE]
These dependencies have not received updates for an extended period and may be unmaintained:
View abandoned dependencies (5)
| Datasource | Name | Last Updated |
|---|---|---|
| npm | clipboard |
2022-05-04 |
| npm | eventemitter3 |
2023-04-30 |
| npm | htm |
2022-04-26 |
| npm | react-table |
2022-05-16 |
| npm | slugify |
2023-03-26 |
Packages are marked as abandoned when they exceed the abandonmentThreshold since their last release.
Unlike deprecated packages with official notices, abandonment is detected by release inactivity.
Pending Approval
The following branches are pending approval. To create them, click on a checkbox below.
- chore(deps): pin dependency shiki to v1.14.1
- chore(deps): update dependency shiki to v3
- fix(deps): update dependency marked to v17
- fix(deps): update react monorepo to v19 (major) (
react,react-dom) - 🔐 Create all pending approval PRs at once 🔐
Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
- chore(deps): update dependency esbuild to ^0.25.0 [security]
- fix(deps): update dependency dompurify to v3.1.3 [security]
- fix(deps): update dependency marked to v11.2.0
- chore(deps): lock file maintenance
- Click on this checkbox to rebase all open PRs at once
Detected dependencies
github-actions
.github/workflows/deploy.yml
npm
package.json
clipboard 2.0.11dompurify 3.0.6eventemitter3 5.0.1htm ^3.1.1marked 11.1.0react ^16.14.0react-dom ^16.14.0react-table ^7.8.0slugify 1.6.6esbuild ^0.23.1shiki ^1.14.1
renovate-config-presets
renovate.json
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The dashboard names package.json, renovate.json, and .github/workflows/deploy.yml; start by reviewing the pending approvals and linked pull requests #49, #43, #30, and #36. There is no standalone requested change or completion condition; work would require selecting and validating specific dependency updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, react
- Domain
- ci-cd, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100