[Regression]: start_timestamp column of history command is not a datetime #17666
Description
Bug report form
- I have done a basic search of the issue tracker to find any existing issues that are similar.
- I have checked that my version is at least the latest stable release available via my installation method.
Describe the bug
The start_timestamp column of the history command is an integer in the current nushell git build.
How to reproduce
Dev build:
❯ history | last
╭─────────────────┬──────────────────────────────────╮
│ start_timestamp │ 1772208749948 │
│ command │ history | last │
│ cwd │ /data/data/com.termux/files/home │
│ duration │ │
│ exit_status │ │
╰─────────────────┴──────────────────────────────────╯Version 0.110.0:
❯ history | last
╭─────────────────┬──────────────────────────────────╮
│ start_timestamp │ now │
│ command │ history | last │
│ cwd │ /data/data/com.termux/files/home │
│ duration │ 0sec │
│ exit_status │ 0 │
╰─────────────────┴──────────────────────────────────╯Expected behavior
It should be a datetime like 0.110.0
Configuration
| key | value |
|---|---|
| version | 0.110.1 |
| major | 0 |
| minor | 110 |
| patch | 1 |
| branch | main |
| commit_hash | 1d11c95 |
| build_os | linux-x86_64 |
| build_target | aarch64-linux-android |
| rust_version | rustc 1.91.1 (ed61e7d7e 2025-11-07) |
| rust_channel | 1.91.1-x86_64-unknown-linux-gnu |
| cargo_version | cargo 1.91.1 (ea2d97820 2025-10-10) |
| build_time | 2026-02-21 20:49:41 +00:00 |
| build_rust_channel | release |
| allocator | standard |
| features | default, mcp, network, plugin, rustls-tls, sqlite, trash-support |
| installed_plugins | |
| experimental_options | example=false, reorder-cell-paths=true, pipefail=true, enforce-runtime-annotations=false |