Upgrading Versions | Bootspring Docs

Guide to upgrading Bootspring between versions.

Checking Your Version#

bootspring --version

Upgrade Process#

Step 1: Check Current Version#

bootspring --version
# Output: bootspring/1.1.0

Step 2: Check for Updates#

bootspring update --check

Output:

Current version: 1.1.0
Latest version: 1.2.0

Changelog:
- New: Preseed workflow
- New: 5 additional agents
- Improved: Context generation performance
- Fixed: Memory leak in long sessions

Run `bootspring update` to upgrade.

Step 3: Backup Configuration#

cp bootspring.config.js bootspring.config.js.backup
cp -r .bootspring .bootspring.backup

Step 4: Update#

# Using npm
npm update -g bootspring

# Or using the CLI
bootspring update

Step 5: Verify#

bootspring --version
bootspring status

Version Numbering#

Bootspring follows semantic versioning:

MAJOR.MINOR.PATCH

Type	Description	Example
Major	Breaking changes	1.0.0 → 2.0.0
Minor	New features, backwards compatible	1.1.0 → 1.2.0
Patch	Bug fixes	1.1.0 → 1.1.1

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:

module.exports = {
  agents: ['frontend-expert', 'backend-expert'],
};

New config:

module.exports = {
  agents: {
    enabled: ['frontend-expert', 'backend-expert'],
  },
};

Migration:

bootspring config migrate

Command Changes#

Old	New
`bootspring agent frontend-expert`	`bootspring agent invoke frontend-expert`
`bootspring skill patterns/auth`	`bootspring skill apply patterns/auth`

API Changes#

Check SDK documentation for API changes.

Migration Commands#

# Check for migration needs
bootspring migrate --check

# Run automatic migration
bootspring migrate

# Manual review of changes
bootspring migrate --dry-run

Minor Version Upgrades#

Minor versions add features without breaking changes.

Typical Process#

npm update -g bootspring
bootspring --version

No configuration changes needed.

New Features#

Check what's new:

bootspring changelog

Patch Version Upgrades#

Patches contain bug fixes only.

Auto-Update#

Enable auto-updates for patches:

// bootspring.config.js
module.exports = {
  updates: {
    autoUpdate: 'patch', // 'none', 'patch', 'minor', 'all'
    checkInterval: 'daily',
  },
};

Manual Update#

npm update -g bootspring

Version Pinning#

Pin to Specific Version#

npm install -g bootspring@1.2.0

Pin in CI/CD#

# GitHub Actions
- run: npm install -g bootspring@1.2.0

Lock File#

For team consistency:

// .bootspringrc
{
  "version": "1.2.0",
  "checkOnStart": false
}

Rollback#

Rollback to Previous Version#

# Install specific version
npm install -g bootspring@1.1.0

# Restore backup config
cp bootspring.config.js.backup bootspring.config.js
cp -r .bootspring.backup/* .bootspring/

Clear Cache After Rollback#

bootspring cache clear

Beta and Canary Versions#

Installing Beta#

npm install -g bootspring@beta

Installing Canary#

npm install -g bootspring@canary

Switching Back to Stable#

npm install -g bootspring@latest

Multi-Project Upgrades#

Check All Projects#

# In each project directory
for dir in ~/projects/*/; do
  cd "$dir"
  if [ -f "bootspring.config.js" ]; then
    echo "Project: $dir"
    bootspring --version
  fi
done

Upgrade All#

# Global upgrade affects all projects
npm update -g bootspring

Project-Specific Versions#

Use npx for project-specific versions:

// package.json
{
  "devDependencies": {
    "bootspring": "1.2.0"
  }
}

npx bootspring <command>

Troubleshooting Upgrades#

Config Validation Failed#

bootspring config validate
# Shows specific issues

bootspring config fix
# Attempts auto-fix

Context Generation Changed#

Regenerate context after major upgrades:

bootspring generate --force

Cache Issues#

Clear cache if experiencing issues:

bootspring cache clear

Plugin Compatibility#

Check plugin compatibility:

bootspring plugin list
# Shows if plugins need updates

bootspring plugin update --all

Release Channels#

Channel	Description	Stability
`stable`	Production ready	High
`beta`	Feature complete, testing	Medium
`canary`	Latest features, may be unstable	Low

Changelog#

View changelog:

bootspring changelog

# Specific version
bootspring changelog 1.2.0

# Range
bootspring changelog 1.1.0..1.2.0

Or visit /changelog on the website.