portabletext / portabletext/react-portabletext
Dependency Dashboard
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 377
- Forks
- 31
- Avg merge
- 23h 42m
- Merged PRs (30d)
- 9
Description
This issue lists Renovate updates and detected dependencies. More settings and logs here.
Using a curated preset maintained by
Sanity: The Content Operating System
Awaiting Schedule
The following updates are awaiting their schedule. To get an update now, click on a checkbox below.
- chore(deps): update dependency vitest to v5
- chore(deps): update pnpm to v11
- chore(deps): update pnpm to v12
- 🔐 Create all awaiting schedule 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 non-major (
@sanity/client,@sanity/tsdown-config,@sanity/ui,@types/react,@types/react-dom,groq,oxc-transform-react,oxfmt,oxlint,oxlint-tsgolint,portabletext/.github,react,react-dom,react-is,sanity,tsdown,vite) - chore(deps): lock file maintenance
- Click on this checkbox to rebase all open PRs at once
PR Closed (Blocked)
The following updates are blocked by an existing closed PR. To recreate the PR, click on a checkbox below.
- chore(deps): update actions/create-github-app-token action to v3
- chore(deps): update dependency @changesets/changelog-github to v1
- chore(deps): update dependency @changesets/cli to v3
- chore(deps): update pnpm/action-setup action to v5
- chore(deps): update pnpm/action-setup action to v6
Detected Dependencies
github-actions (5)
.github/workflows/deploy.yml (5)
actions/create-github-app-token v2→ [Updates:v3]actions/checkout v7pnpm/action-setup v4→ [Updates:v5,v6]actions/setup-node v7peaceiris/actions-gh-pages v4@84c30a85c19949d7eee79c4ff27748b70285e453.github/workflows/format-if-needed.yml (1)
portabletext/.github main@a311e91e5c045a8986adf91bb0d3e35808e1704c→ [Updates:main].github/workflows/main.yml (9)
actions/checkout v7pnpm/action-setup v4→ [Updates:v5,v6]actions/setup-node v7actions/checkout v7pnpm/action-setup v4→ [Updates:v5,v6]actions/setup-node v7actions/checkout v7pnpm/action-setup v4→ [Updates:v5,v6]actions/setup-node v7.github/workflows/release.yml (1)
portabletext/.github main@a311e91e5c045a8986adf91bb0d3e35808e1704c→ [Updates:main].github/workflows/renovate.yml (1)
portabletext/.github main@a311e91e5c045a8986adf91bb0d3e35808e1704c→ [Updates:main]
npm (1)
package.json (38)
@portabletext/toolkit ^6.0.0@portabletext/types ^4.0.2@changesets/changelog-github ^0.7.0→ [Updates:^1.0.1]@changesets/cli ^2.31.1→ [Updates:^3.0.3]@sanity/client ^8.4.0→ [Updates:^8.6.2]@sanity/image-url ^2.1.1@sanity/tsconfig ^2.2.1@sanity/tsdown-config ^0.27.1→ [Updates:^0.28.0]@sanity/ui ^4.0.7→ [Updates:^4.2.1]@types/leaflet ^1.9.22@types/react ^19.2.18→ [Updates:^19.3.0]@types/react-dom ^19.2.5→ [Updates:^19.3.0]@types/ws ^8.18.1@vitejs/plugin-react ^6.1.1esbuild ^0.28.2esbuild-register ^3.6.0groq ^6.12.0→ [Updates:^6.15.0]leaflet ^1.9.4oxc-transform-react ^0.147.0→ [Updates:^0.150.0]oxfmt ^0.66.0→ [Updates:^0.68.0]oxlint ^1.81.0→ [Updates:^1.83.0]oxlint-tsgolint ^7.0.2001→ [Updates:^7.0.2002]react ^19.2.8→ [Updates:^19.3.0]react-dom ^19.2.8→ [Updates:^19.3.0]react-is ^19.2.8→ [Updates:^19.3.0]react-leaflet ^5.0.0react-refractor ^4.0.0refractor ^5.0.0rimraf ^5.0.1sanity ^6.12.0→ [Updates:^6.15.0]styled-components ^6.5.3tsdown ^0.22.14→ [Updates:^0.23.0]typescript 7.0.2vite ^8.2.2→ [Updates:^8.3.0]vitest ^4.1.11→ [Updates:^5.0.1]react ^19node >=22.12pnpm 10.34.5→ [Updates:11.27.0,12.4.2]
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 the Renovate dashboard entries for .github/workflows/*.yml and package.json, then inspect the linked open and closed dependency-update PRs. The issue does not define a single change or completion condition; any work would need to be scoped from those existing updates and validated through the repository's checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js, react, typescript, vite
- Domain
- build-system, ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100