dextinity-minor-update

Bumps all @dextinity/* packages to the newest minor or patch version within the current major.

52|9|Updated Mar 4, 2019
One-click install
npx skills add https://github.com/vivid-planet/dextinity --skill dextinity-minor-update-vivid-planet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dextinity-minor-update
Source: https://github.com/vivid-planet/dextinity/tree/main/skills/dextinity-minor-update
Command: npx skills add https://github.com/vivid-planet/dextinity --skill dextinity-minor-update-vivid-planet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Updating a Dextinity project is tedious because the repo root, api/, admin/, and any site packages each have their own package.json and package-lock.json, and every core @dextinity/* dependency must be pinned to the same exact version. This Skill automates finding, bumping, installing, and verifying a minor or patch update across all of them. ## Core Features & Use Cases - Cross-package discovery: Finds every @dextinity/* dependency in the root, api/, admin/, and any site packages (detected by content, not path), and distinguishes core packages from non-core ones. - Safe version targeting: Queries npm for the newest stable version in the current major, filtering out canary, beta, and rc pre-releases. - Install and verification: Runs npm install in each directory, verifies lockfiles moved, and runs lint/tests with --if-present, reporting failures without attempting risky fixes. - Use Case: You ask to "update Dextinity to the latest 8.x" — the Skill bumps 8.20.4 to 8.21.0 in every package.json, installs in each directory, runs lint and tests, and reminds you to start the dev server so generated files refresh. ## Quick Start Ask the assistant to update all Dextinity packages in this project to the latest minor or patch version of the current major.

Frequently Asked Questions about dextinity-minor-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update all Dextinity packages to the latest minor version?

Find every @dextinity/* entry in the root, api/, admin/, and site package.json files, query npm for the newest stable version in the current major, pin all core packages to it, then run npm install in each directory. This Skill automates that full workflow including verification.

How do I find site packages in a Dextinity project?

Search for package.json files outside node_modules that depend on @dextinity/site-nextjs or @dextinity/site-react, since site locations are not guaranteed. A project may have zero, one, or many site packages, and an empty result is valid.

Can this Skill upgrade Dextinity across major versions?

No, it only covers minor and patch updates within the current major, such as 8.20.4 to 8.21.0. Major upgrades like 8.x to 9.x involve breaking changes, codemods, and migration guides, so the Skill stops and tells the user instead.

Why must @dextinity packages use pinned versions without caret or tilde?

Core @dextinity/* packages are released together and must all be pinned to the same exact version across every package.json. A caret or tilde on a core package means the project is in a broken state, and the Skill stops rather than bumping over it.

What happens if npm install fails during a Dextinity update?

The Skill stops immediately and reports the failing directory, exact error lines, and the state of the already-edited package.json files. It never uses --force, --legacy-peer-deps, or manual lockfile edits, since failures often indicate real incompatibilities the user must diagnose.

Why do type errors appear after a Dextinity minor update?

Type errors often come from stale generated files like block-meta.json or the GraphQL schema, which only regenerate when the app boots. Starting the dev server once after the update usually resolves them before assuming the bump broke anything.