DevExpress / DevExpress/devextreme-nextjs-template
Dependency Dashboard
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 1
- Forks
- 4
- Avg merge
- 6h 46m
- Merged PRs (30d)
- 3
Description
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
View this repository on the Mend.io Web Portal.
Rate-Limited
The following updates are currently rate-limited. To force their creation now, click on a checkbox below.
- chore(deps): update nextjs monorepo to v16.3.5 (
eslint-config-next,next) - chore(deps): update pnpm to v11.27.0
- fix(deps): update dependency jose to v6.2.12
- chore(deps): update dependency eslint to v10
- chore(deps): update dependency nanoid@<3.3.17 to v6
- chore(deps): update pnpm to v12
- 🔐 Create all rate-limited PRs at once 🔐
Pending Status Checks
The following updates await pending status checks. To force their creation now, click on a checkbox below.
- chore(deps): update dependency devextreme-themebuilder to v26.1.5
- fix(deps): update dependency devextreme to v26.1.5
- fix(deps): update dependency devextreme-react to v26.1.5
Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
- chore(deps): update node.js to v24.21.0
- fix(deps): update react monorepo to v19.3.0 (
react,react-dom) - Click on this checkbox to rebase all open PRs at once
Detected Dependencies
asdf (1)
.tool-versions (2)
node 24.15.0→ [Updates:24.21.0]pnpm 11.7.0→ [Updates:11.27.0,12.5.1]
github-actions (1)
.github/workflows/repository-check.yml (1)
DevExpress/github-actions repository-check
mise (1)
.mise.toml (2)
node 24.15.0→ [Updates:24.21.0]pnpm 11.7.0→ [Updates:11.27.0,12.5.1]
nodenv (1)
.node-version (1)
node 24.15.0→ [Updates:24.21.0]
npm (2)
package.json (12)
devextreme 26.1.4→ [Updates:26.1.5]devextreme-react 26.1.4→ [Updates:26.1.5]jose 6.1.3→ [Updates:6.2.12]next ^16.3.3→ [Updates:^16.3.3]react 19.2.3→ [Updates:19.3.0]react-dom 19.2.3→ [Updates:19.3.0]devextreme-cli 1.17.0devextreme-themebuilder 26.1.4→ [Updates:26.1.5]eslint ^9.39.5→ [Updates:^10.0.0]eslint-config-next ^16.3.3→ [Updates:^16.3.3]node ^24.15.0→ [Updates:^24.21.0]pnpm 11.7.0+sha512.19cc852c120c7125760f2443ee6be0ca5b40f9f50598de1a09a1f177503e010e57c23c77646e01e761de59bf874fb22a3398c33ab9691fc13eb946b6f0f4d620→ [Updates:11.27.0,12.5.1]pnpm-workspace.yaml (4)
brace-expansion@<=5.0.8 ^5.0.9nanoid@<3.3.17 ^3.3.17→ [Updates:^6.0.0]postcss@<8.5.10 ^8.5.10sharp@<0.35.0 ^0.35.0
renovate-config (1)
.github/renovate.json
- Check this box to trigger a request for Renovate to run again on this repository
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
Start with package.json, pnpm-workspace.yaml, .tool-versions, .mise.toml, .node-version, and .github/workflows/repository-check.yml, then review the linked Renovate pull requests. This dashboard contains multiple rate-limited, pending, and open dependency updates rather than one scoped change. Done would require determining which updates are appropriate and verifying the repository checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, nextjs, nodejs, react
- Domain
- ci-cd, devops, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100