Skip to content

chore: Release hotdata-cli version 0.16.0 - #222

Merged
eddietejeda merged 2 commits into
mainfrom
chore/release-0.16.0
Jul 10, 2026
Merged

eddietejeda merged 2 commits into
mainfrom
chore/release-0.16.0

Conversation

@eddietejeda

Copy link
Copy Markdown
Contributor

Summary

  • Bumps version to 0.16.0 in Cargo.toml and all skill files
  • Adds 0.16.0 entry to CHANGELOG.md

Changes in this release

  • tables list scoped to active database; --table, --limit, --cursor all work within that scope
  • New tables show <schema.table> subcommand
  • New results show <id> subcommand
  • indexes list scoped to active database connection; --connection-id removed
  • indexes delete uses --catalog instead of --connection-id
  • search --table accepts schema.table (active DB) or catalog.schema.table
  • hotdata connections command removed

Comment thread Cargo.toml
[package]
name = "hotdata-cli"
version = "0.15.0"
version = "0.16.0"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This bumps the package to 0.16.0, but Cargo.lock still pins hotdata-cli at 0.15.0 (line 1191) and is not included in this PR. The lockfile is out of sync with Cargo.toml.

This matters for a release PR: any cargo invocation run with --locked/--frozen (and cargo publish) will fail against a stale lockfile, and the committed Cargo.lock no longer reflects the released version. Please run cargo update -p hotdata-cli (or a plain cargo build) and commit the updated Cargo.lock so it reads version = "0.16.0".

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review

Blocking Issues

  • Cargo.toml:3 bumps the version to 0.16.0, but Cargo.lock still pins hotdata-cli at 0.15.0 and is not part of this PR. The lockfile is out of sync with the version bump.

Action Required

  • Regenerate and commit Cargo.lock (e.g. cargo update -p hotdata-cli or a plain cargo build) so it reflects 0.16.0, then include it in this release PR. A stale lockfile will break any --locked/--frozen build and cargo publish.

@codecov

codecov Bot commented Jul 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cycle 1 blocking issue resolved: Cargo.lock is now included and updated to 0.16.0, in sync with Cargo.toml. Version bumps are consistent across all skill files and the CHANGELOG entry is well-formed. LGTM.

@eddietejeda
eddietejeda merged commit d9381fd into main Jul 10, 2026
14 checks passed
@eddietejeda
eddietejeda deleted the chore/release-0.16.0 branch July 10, 2026 05:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant