Skip to content

Release v1.0.1

Choose a tag to compare

@github-actions github-actions released this 05 Nov 09:31
· 12 commits to master since this release
v1.0.1
340ba70

Release Date: November 5, 2025

🆕 What's New

Architecture Filtering

Added support for filtering instances by CPU architecture, allowing you to find instances that match your specific architecture requirements.

✨ New Features

--arch Parameter

  • Filter instances by CPU architecture
  • Supported values: x86_64 or arm64
  • Works in combination with other filters (CPU, memory, family)

Architecture in JSON Output

  • Added arch field to JSON output format
  • Enables programmatic filtering and analysis by architecture

📋 Usage Examples

Filter by Architecture

# Find x86_64 instances
./spot-instance-advisor \
  --accessKeyId YOUR_KEY \
  --accessKeySecret YOUR_SECRET \
  --arch x86_64 \
  --json

# Find ARM64 instances
./spot-instance-advisor \
  --accessKeyId YOUR_KEY \
  --accessKeySecret YOUR_SECRET \
  --arch arm64 \
  --mincpu 2 \
  --maxcpu 8 \
  --json

Combined Filtering

# Find ARM64 instances in specific families
./spot-instance-advisor \
  --accessKeyId YOUR_KEY \
  --accessKeySecret YOUR_SECRET \
  --family ecs.n1,ecs.n2 \
  --arch arm64 \
  --limit 10 \
  --json

📝 JSON Output Format

The JSON output now includes the arch field:

[
  {
    "instanceTypeId": "ecs.n1.small",
    "zoneId": "cn-hangzhou-a",
    "pricePerCore": 0.1234,
    "discount": 2.5,
    "possibility": 0.8,
    "cpuCoreCount": 1,
    "memorySize": 2.0,
    "instanceFamily": "ecs.n1",
    "arch": "x86_64"
  }
]

📚 Documentation Updates

  • Updated README.md with --arch parameter documentation
  • Updated USAGE.md with architecture filtering examples
  • Added architecture filtering to all relevant examples

🔄 Migration Notes

This is a backward-compatible release. Existing scripts and workflows will continue to work without changes. The --arch parameter is optional and defaults to no architecture filtering.


Full Changelog: v1.0.0...v1.0.1