version command

Display version information for ao-forge and related tools.

Syntax

ao-forge version [options]

Options

OptionDescriptionDefault
--verboseShow detailed version informationfalse
--jsonOutput in JSON formatfalse
--helpShow help information-

Examples

Basic Usage

# Show version information
ao-forge version

# Show detailed version information
ao-forge version --verbose

# Output in JSON format
ao-forge version --json

Version Information

ao-forge Version

# Show ao-forge version
ao-forge version

# Output example:
# ao-forge: 1.0.0
# Node.js: 18.17.0
# npm: 9.6.7

Detailed Version Information

# Show detailed version information
ao-forge version --verbose

# Output example:
# ao-forge: 1.0.0
# Node.js: 18.17.0
# npm: 9.6.7
# AOS CLI: 1.0.0
# Framework: Next.js 15.0.0
# Package Manager: pnpm 8.6.10

JSON Output

# Output in JSON format
ao-forge version --json

# Output example:
# {
#   "ao-forge": "1.0.0",
#   "node": "18.17.0",
#   "npm": "9.6.7",
#   "aos": "1.0.0",
#   "framework": "Next.js 15.0.0",
#   "packageManager": "pnpm 8.6.10"
# }

Version Checking

Check for Updates

# Check for ao-forge updates
ao-forge version --check-updates

# Check for all tool updates
ao-forge version --check-updates --all

Update Information

# Show update information
ao-forge version --update-info

# Show update information for specific tool
ao-forge version --update-info --tool aos

Version Compatibility

Check Compatibility

# Check version compatibility
ao-forge version --check-compatibility

# Check compatibility with specific version
ao-forge version --check-compatibility --version 1.0.0

Compatibility Matrix

# Show compatibility matrix
ao-forge version --compatibility-matrix

# Output example:
# ao-forge 1.0.0:
#   Node.js: >=18.0.0
#   AOS CLI: >=1.0.0
#   Next.js: >=15.0.0
#   Nuxt.js: >=3.0.0

Version History

Show Version History

# Show version history
ao-forge version --history

# Show version history for specific tool
ao-forge version --history --tool aos

Changelog

# Show changelog
ao-forge version --changelog

# Show changelog for specific version
ao-forge version --changelog --version 1.0.0

Version Management

Set Version

# Set version for project
ao-forge version --set 1.0.0

# Set version with tag
ao-forge version --set 1.0.0 --tag "stable"

Version Bumping

# Bump patch version
ao-forge version --bump patch

# Bump minor version
ao-forge version --bump minor

# Bump major version
ao-forge version --bump major

Version Information Sources

ao-forge Version

  • Package version - From package.json
  • Git commit - From git repository
  • Build date - From build process
  • Environment - From runtime environment
  • Node.js - Runtime version
  • npm/pnpm/yarn - Package manager version
  • AOS CLI - AO process management tool
  • Framework - Next.js or Nuxt.js version

Version Display Formats

Default Format

ao-forge: 1.0.0
Node.js: 18.17.0
npm: 9.6.7

Verbose Format

ao-forge: 1.0.0
Node.js: 18.17.0
npm: 9.6.7
AOS CLI: 1.0.0
Framework: Next.js 15.0.0
Package Manager: pnpm 8.6.10
Git Commit: abc1234
Build Date: 2024-01-01T00:00:00Z

JSON Format

{
  "ao-forge": "1.0.0",
  "node": "18.17.0",
  "npm": "9.6.7",
  "aos": "1.0.0",
  "framework": "Next.js 15.0.0",
  "packageManager": "pnpm 8.6.10",
  "gitCommit": "abc1234",
  "buildDate": "2024-01-01T00:00:00Z"
}

Version Requirements

Minimum Requirements

  • Node.js - >=18.0.0
  • npm - >=8.0.0
  • AOS CLI - >=1.0.0
  • Node.js - 18.17.0 or later
  • npm - 9.6.7 or later
  • AOS CLI - 1.0.0 or later

Version Troubleshooting

Common Issues

  1. Version not found
    Error: Version information not available
Solution: Check if ao-forge is properly installed
  2. Incompatible version
    Error: Incompatible version detected
Solution: Update to a compatible version
  3. Version check failed
    Error: Version check failed
Solution: Check internet connection and try again

Best Practices

Version Management

  1. Keep versions updated regularly
  2. Check compatibility before updates
  3. Use semantic versioning for releases
  4. Document version changes in changelog
  5. Test versions before deployment

Version Display

  1. Use appropriate format for your needs
  2. Include relevant information in version output
  3. Make version information easily accessible
  4. Update version information regularly
  5. Use consistent versioning across tools
Table of Contents