Upgrading Versions

Guide to upgrading Bootspring between versions.

Checking Your Version#

Upgrade Process#

Step 1: Check Current Version#

Step 2: Check for Updates#

Output:

Step 3: Backup Configuration#

Step 4: Update#

Step 5: Verify#

Version Numbering#

Bootspring follows semantic versioning:

Major Version Upgrades#

Major versions may include breaking changes.

Pre-Upgrade Checklist#

• Read the changelog
• Backup configuration
• Check deprecation warnings
• Review migration guide
• Test in development first

Common Breaking Changes#

Configuration Schema Changes#

Old config:

New config:

Migration:

Command Changes#

API Changes#

Check SDK documentation for API changes.

Migration Commands#

Minor Version Upgrades#

Minor versions add features without breaking changes.

Typical Process#

No configuration changes needed.

New Features#

Check what's new:

Patch Version Upgrades#

Patches contain bug fixes only.

Auto-Update#

Enable auto-updates for patches:

Manual Update#

Version Pinning#

Pin to Specific Version#

Pin in CI/CD#

Lock File#

For team consistency:

Rollback#

Rollback to Previous Version#

Clear Cache After Rollback#

Beta and Canary Versions#

Installing Beta#

Installing Canary#

Switching Back to Stable#

Multi-Project Upgrades#

Check All Projects#

Upgrade All#

Project-Specific Versions#

Use npx for project-specific versions:

Troubleshooting Upgrades#

Config Validation Failed#

Context Generation Changed#

Regenerate context after major upgrades:

Cache Issues#

Clear cache if experiencing issues:

Plugin Compatibility#

Check plugin compatibility:

Release Channels#

Subscribe to Releases#

• Changelog
• Newsletter
• Discord

Changelog#

View changelog:

Or visit /changelog on the website.

Related#

• Troubleshooting
• Configuration
• Changelog