chore(release): align package versions to 0.1.0

[galligan]

Summary

• Align package versions to 0.1.0 across the repo.
• Update changelogs to reflect the new versions.

Changes

• packages/*/package.json
• packages/*/CHANGELOG.md
• apps/outfitter/CHANGELOG.md

Testing

• Not run (not requested).

[galligan]

• fix(errors): avoid TaggedError extends warnings #106 : 2 dependent PRs (#107 , #116 )
• chore(release): align package versions to 0.1.0 #105 👈 (View in Graphite)
• docs: add README and CHANGELOG for testing, kit, outfitter #95
• feat(templates): add daemon project template #94
• feat(templates): add MCP server project template #93
• feat(templates): add CLI project template #92
• fix(cli): implement confirmDestructive prompts #104
• fix(cli): implement createCLI and command builder #103
• feat(kit): add @outfitter/kit meta-package #91
• docs(daemon): add README and CHANGELOG #90
• fix(daemon): fix locking module bugs (GREEN phase) #89
• test(daemon): add locking module tests (RED phase) #88
• feat(daemon): add errors, platform, and locking module stubs #87
• feat(outfitter): add doctor command for environment validation #86
• feat(outfitter): add init command with project scaffolding #85
• feat(daemon): add IPC communication and health checks #84
• feat(daemon): add types and lifecycle management #83
• feat(index): add FTS5 full-text search implementation #82
• feat(index): add types for FTS5 full-text search #81
• feat(testing): add MCP and CLI test harnesses #80
• feat(testing): add test fixture utilities #79
• feat(mcp): add MCP server implementation with typed handlers #78
• feat(mcp): add types and interfaces for MCP server #77
• feat(ui): add Shape discriminated union and render() #76
• feat(ui): add createTokens semantic color layer #75
• feat(state): add pagination helpers #74
• feat(logging): add DEFAULT_PATTERNS for common secret redaction #73
• feat(ui): add formatRelative() for human-readable timestamps #72
• feat(state): add encodeCursor/decodeCursor for pagination #71
• feat(types): add hashId() for deterministic short identifiers #70
• feat(contracts): add Logger.child() and fix AssertionError category #69
• feat(config): centralize environment variable access with Zod validation #42
• fix(logging): enable redaction by default when global rules exist #41
• docs(ui): add README, CHANGELOG, and TSDoc comments #39
• docs(state): add README, CHANGELOG, and TSDoc comments #38
• docs(file-ops): add README, CHANGELOG, and TSDoc comments #37
• docs(logging): add README, CHANGELOG, and TSDoc comments #36
• docs(config): add README, CHANGELOG, and TSDoc comments #35
• fix(cli): enforce cursor TTL #114
• fix(tests): remove placeholder tests #113
• chore(gitattributes): prefer ours for bun lockfiles #115
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[greptile-apps]

Greptile Summary

• Aligns all package versions from 0.0.x to 0.1.0across the monorepo as part of a coordinated release preparation
• Updates corresponding CHANGELOG.md files to document the version alignment and dependency updates
• Includes minor formatting fix in apps/outfitter/CHANGELOG.md by adding proper spacing after section header

Important Files Changed

Filename	Overview
packages/daemon/CHANGELOG.md	Contains duplicate 0.1.0 changelog entries causing version history confusion
packages/config/CHANGELOG.md	Has duplicate 0.1.0 entries with conflicting version information
packages/testing/CHANGELOG.md	Contains duplicate 0.1.0 version entries with different formats and dates

Confidence score: 3/5

• This PR contains formatting issues that could cause confusion in version tracking and break semantic versioning tooling
• Score lowered due to duplicate changelog entries in multiple packages (daemon, config, testing, file-ops, logging, state, cli, ui) where automated changeset entries conflict with existing manual entries
• Pay close attention to all CHANGELOG.md files that now contain duplicate version entries for 0.1.0

Sequence Diagram

sequenceDiagram
    participant Developer as "Developer"
    participant Release as "Release Process"
    participant Packages as "Package Files"
    participant Changelogs as "Changelog Files"
    
    Developer->>Release: "Initiate version alignment to 0.1.0"
    Release->>Packages: "Update version in package.json files"
    Release->>Changelogs: "Add 0.1.0 entries to CHANGELOG.md files"
    Release->>Packages: "Update workspace dependencies to 0.1.0"
    Release->>Developer: "Version alignment complete"

Loading

[greptile-apps]

Additional Comments (6)

1. packages/file-ops/CHANGELOG.md, line 20 (link)

   logic: Duplicate version heading - there are now two ## 0.1.0 entries which will cause confusion in the changelog

2. packages/cli/CHANGELOG.md, line 15-18 (link)

   style: The changelog header now appears after the new version entry instead of at the top - this breaks the standard changelog format where the header should come first

   _{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

3. packages/config/CHANGELOG.md, line 3-20 (link)

   logic: Duplicate version entries for 0.1.0 - the new entry at line 3 conflicts with existing entry at line 20

4. packages/ui/CHANGELOG.md, line 20 (link)

   logic: Duplicate 0.1.0section - there are now two entries for version 0.1.0 (lines 3 and 20)

5. packages/state/CHANGELOG.md, line 3-20 (link)

   logic: There are now two 0.1.0 entries in this changelog - one at line 3 (new) and another at line 20 (existing dated entry). This creates duplicate version entries which violates changelog conventions.

   Should the existing dated entry at line 20 be removed or merged with the new entry?

6. packages/logging/CHANGELOG.md, line 3-19 (link)

   logic: Duplicate version 0.1.0 entries with different dates and formats may confuse users about which features belong to which release

   Should the changeset-generated entry (lines 3-12) replace the manually written one (lines 19-36), or are these meant to represent different releases?

_{25 files reviewed, 8 comments}

_{Edit Code Review Agent Settings | Greptile}

[galligan]

Resolved duplicate 0.1.0 changelog entries by merging version-alignment notes into the existing 0.1.0 sections (added Changed/Dependencies where appropriate). Restacked and resubmitted.

[galligan]

Changelog duplicates are resolved: packages/daemon/CHANGELOG.md and packages/testing/CHANGELOG.md now each have a single 0.1.0 entry.

[galligan]

Merge activity

• Jan 24, 1:54 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jan 24, 3:15 PM UTC: Graphite rebased this pull request as part of a merge.
• Jan 24, 3:15 PM UTC: @galligan merged this pull request with Graphite.