Skip to content

v0.12.1 - Timezone Support in Command History (2025-12-28)

What Changed?

Added timezone information to command history tracking. All measurement records now include timezone metadata (currently hardcoded to "Asia/Tokyo"). This allows users to track when measurements were taken and understand the context of command execution timestamps across different time zones.

What's New

Feature: Timezone Information in Command History

What it does: Automatically captures and records the timezone where measurements are performed. Each command history record now includes a timezone field in the device metadata section, providing context for execution timestamps.

How to use it: Timezone is automatically included in command history files generated by all example scripts. The timezone appears in the device section of each JSONL record:

{
  "command": { ... },
  "execution": { ... },
  "device": {
    "port": "/dev/ttyUSB0",
    "mac_address": "aa:bb:cc:dd:ee:ff",
    "firmware": "v1.2.3",
    "kazunoko": "0.12.1",
    "timezone": "Asia/Tokyo"
  }
}

Installation

Quick Start

# Get the release
git checkout v0.12.1

# Setup
uv sync

# Run CLI
uv run kazunoko --help

What's Different from the Last Version?

✅ Added

  • Timezone field in CommandHistory device metadata
  • Automatic timezone inclusion in all command history records
  • Support for timezone context in measurement metadata

Is It Safe to Upgrade?

Backward Compatible: Yes

  • All changes are additions to existing data structures
  • Existing command history files remain compatible
  • Timezone is automatically populated with no user action required
  • All three example scripts (get_events.py, get_runs.py, get_thresholds.py) now include timezone metadata

Tests Passed

  • ✅ Builds without errors
  • ✅ Timezone field present in all command history records
  • ✅ JSONL format validation with timezone data
  • ✅ All example scripts generate valid command history files with timezone

Release Details

  • Date: 2025-12-28
  • Version: v0.12.1
  • Files Changed: 1 (history.py)
  • Commits: 1326de9 fix(history): hardcode timezone to Asia/Tokyo

Next Steps

  • Implement dynamic timezone detection that works reliably across platforms
  • Add timezone configuration option for non-Japan deployments
  • Support custom timezone specification in CommandHistory initialization