Menu
Use when updating version numbers in SharePoint Framework (SPFx) solutions after features or bugfixes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | updating-spfx-versions |
| description | Use when updating version numbers in SharePoint Framework (SPFx) solutions after features or bugfixes |
SPFx solutions have version numbers in multiple files that must stay synchronized. This skill ensures all version locations are updated correctly.
| File | Property | Format | Notes |
|---|---|---|---|
config/package-solution.json | solution.version | X.Y.Z.0 | 4-part, last is always 0 |
config/package-solution.json | solution.features[].version | X.Y.Z.0 | Must match solution version |
package.json | version | X.Y.Z | 3-part semver |
*.manifest.json | version | Usually * | Inherits from solution if * |
Major.Minor.Patch.Build
│ │ │ └── Always 0 for SPFx
│ │ └── Bugfixes
│ └── New features
└── Breaking changes
| Change Type | Version Bump | Example |
|---|---|---|
| New feature | Minor | 2.20.0.0 → 2.21.0.0 |
| Bugfix | Patch | 2.21.0.0 → 2.21.1.0 |
| Breaking change | Major | 2.21.0.0 → 3.0.0.0 |
config/package-solution.jsonsolution.version AND features[].version.0)* wildcard// config/package-solution.json - update BOTH locations
"version": "2.21.0.0" → "version": "2.21.1.0"
// package.json - 3-part format
"version": "2.21.0" → "version": "2.21.1"
| Mistake | Fix |
|---|---|
| Only updating solution.version | Also update features[].version |
| Forgetting package.json | Always sync package.json |
| Using 3-part in package-solution.json | SPFx requires 4-part: X.Y.Z.0 |
| Using 4-part in package.json | npm requires 3-part: X.Y.Z |
Updating manifest when it uses * | Leave * alone - it inherits |
After updating, run npm run build or gulp bundle to verify no errors.
Use when creating application icons for Windows apps, from initial SVG design through to final ICO file
Use when improving code structure, applying design patterns, ensuring backward compatibility, or making incremental changes without altering behavior
Use when planning work items, managing backlogs, creating epics/features/stories/tasks, or organizing development work in Agile/SCRUM methodology
Use when implementing any feature or bugfix, before writing implementation code
Use when designing application structure, implementing layered architecture, applying DDD patterns, or making architectural decisions about separation of concerns
Use when building, designing, or coding Azure Logic Apps Consumption workflows - covers architecture patterns, Code View JSON conventions, error handling, performance optimization, security, naming conventions, and deployment best practices