Skip to content

chore: release 0.15.0 - #243

Merged
brendanjryan merged 1 commit into
mainfrom
changelog-release/main
Oct 23, 2026
Merged

brendanjryan merged 1 commit into
mainfrom
changelog-release/main

Conversation

@tempo-github-sts

@tempo-github-sts tempo-github-sts Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Version wallet-cli to 0.15.0 and update CHANGELOG.md.

@tempoxyz-bot

tempoxyz-bot commented Oct 15, 2026 •

Copy link
Copy Markdown

✅ Cyclops Security Review: safe to merge

Last reviewed: f2c7fb1 (latest) · no open findings

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from 9724a9a to d6dcc71 Compare October 15, 2026 20:19
@tempo-github-sts tempo-github-sts Bot changed the title chore: release 0.14.1 chore: release 0.15.0 Oct 15, 2026
@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch 13 times, most recently from 42c9859 to 6bd1028 Compare October 16, 2026 03:46

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. This is a mechanical release commit for 0.15.0.
What was reviewed:

  • Compared all 12 deleted changesets marked minor or patch against the new CHANGELOG.md entries. Each text is copied word for word and filed at the right level. The 5 none changesets are correctly left out.
  • Two of the changesets are keyed tempo-request: rather than wallet-cli:. That is expected: .changelog/config.toml lists it as an alias of the single shared wallet-cli package, so including them here is correct.
  • The package.json version (0.14.0 to 0.15.0) matches the new heading, and the date 2026-10-16 comes after the 0.14.0 entry. No other file still references 0.14.0.
Extended reasoning...

The change deletes 17 pending changeset files, adds their text as a new 0.15.0 section in CHANGELOG.md, and bumps the version in package.json. It contains no source code and touches nothing security-sensitive. The changelog text matches the deleted changesets exactly, and each entry sits under the right minor or patch heading. The timeline shows no outstanding reviewer objections, and the bug hunt ended with dry_streak.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch 2 times, most recently from 31edc71 to 847a4cc Compare October 16, 2026 03:58

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. This is a mechanical release commit for 0.15.0.

What was reviewed:

  • All 14 non-none changesets appear exactly once in CHANGELOG.md, under the heading that matches their bump, with their text intact. That includes the multi-paragraph logout-safety and whoami-keys-chain-state entries. The 6 none changesets are left out, as they should be.
  • The private-file-chmod.md changeset is the "pending login no longer fails with ENOENT" patch entry, so it was not dropped.
  • tempo-request: entries belong in this changelog: scripts/changelog.ts lists tempo-request as an allowed package name, and the tempo-request bin ships from this package. Minor is the highest bump, so going from 0.14.0 to 0.15.0 is correct.
Extended reasoning...

The change bumps the version in package.json, deletes the 20 pending .changelog/ files and adds a 0.15.0 section to CHANGELOG.md. No source code changes. It touches no security-sensitive surface and no CODEOWNERS file covers these paths. I compared each deleted changeset's bump and text against the generated section and found no omissions, duplicates or edits. The version bump matches the highest bump among the changesets, which is minor.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch 3 times, most recently from 3021673 to c5370b2 Compare October 16, 2026 17:59

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. This is a mechanical 0.15.0 release: the package.json version goes up and the pending changesets are folded into CHANGELOG.md.

What was reviewed:

  • All 24 deleted changesets are accounted for. The 7 minor ones are under Minor Changes and the 10 patch ones are under Patch Changes, with the text unchanged. The 7 none changesets (internal refactors and test changes) are correctly left out.
  • The tempo-request changesets count toward wallet-cli, because .changelog/config.toml lists tempo-request as an alias of that single package.
  • Going from 0.14.0 to 0.15.0 is the right bump for a pre-1.0 release with minor and breaking entries. The section date matches the commit.
Extended reasoning...

The change touches only release metadata: it deletes 24 .changelog/*.md changesets, adds a 0.15.0 section to CHANGELOG.md, and bumps version in package.json. No source code, auth, crypto or permission logic changes, and no CODEOWNERS file covers these paths. Each changeset's bump type matches the section its text landed in, and the total of 7 minor, 10 patch and 7 none comes to all 24 files. The timeline shows no outstanding change requests from other reviewers.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from c5370b2 to 980f863 Compare October 16, 2026 19:05

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. This is a mechanical release commit: the version goes up to 0.15.0 and the pending changesets are moved into CHANGELOG.md.

What was reviewed:

  • All 25 deleted .changelog/ files against the new 0.15.0 section. The 18 user-facing changesets (8 minor, 10 patch) appear word for word. The 7 left out are all marked none and are internal: compat modules, errors registry, the three split refactors, the doctor test budget and the subprocess network guard.
  • The package.json bump from 0.14.0 to 0.15.0. No other file in the repo mentions the version.
  • The release heading date (2026-10-16), which sits directly above 0.14.0 (2026-10-15).
Extended reasoning...

The change touches only release metadata: it deletes 25 changeset files, adds a 0.15.0 section to CHANGELOG.md and bumps the version in package.json. It contains no source code and touches no security-sensitive surface. Every user-facing changeset maps one-to-one onto a CHANGELOG entry with identical text, and the omitted ones are all marked none (internal). There is no CODEOWNERS file, no open CHANGES_REQUESTED review appears in the timeline, and the bug hunt ran until it stopped finding anything (dry_streak).

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from 980f863 to 5594c71 Compare October 16, 2026 19:20

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. This is a routine 0.15.0 release commit and it changes no code.
What was reviewed:

  • Every deleted changeset was matched to CHANGELOG.md. All 9 minor and 10 patch changesets appear word for word in the section that matches their bump level, including private-file-chmod (the ENOENT patch entry).
  • The 7 changesets that are not in the changelog (compat-modules, doctor-test-timeout, errors-registry, split-commands, split-request, split-sessions-transfer, subprocess-network-guard) are all marked none and describe internal-only changes, so leaving them out looks intentional.
  • package.json goes from 0.14.0 to 0.15.0, and no other copy of 0.14.0 remains outside the old CHANGELOG heading. The 2026-10-16 date comes after the 0.14.0 date of 2026-10-15.
Extended reasoning...

The change deletes 26 changeset files under .changelog/, adds a 0.15.0 section to CHANGELOG.md, and bumps the version field in package.json. It touches no source code and no security-sensitive surface. Every changeset at minor or patch level is carried into CHANGELOG.md verbatim, and the only ones left out are marked none. The repository has no CODEOWNERS file and the timeline shows no outstanding objection from another reviewer. The bug hunt ended with dry_streak and reported no findings.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from 5594c71 to 4e5e653 Compare October 17, 2026 02:39

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. This is a mechanical release commit for 0.15.0.

What was reviewed:

  • Compared each of the 26 deleted .changelog/ files with the new CHANGELOG section. All 9 minor and 10 patch changesets appear under the right heading with matching text, including private-file-chmod (the ENOENT patch bullet).
  • The other 7 changesets with no bullet (compat-modules, doctor-test-timeout, errors-registry, split-commands, split-request, split-sessions-transfer, subprocess-network-guard) are all marked none (internal-only), so leaving them out is correct.
  • The package.json bump from 0.14.0 to 0.15.0 matches the new ## 0.15.0 (2026-10-17) heading.
Extended reasoning...

The change deletes 26 changeset files, adds a 0.15.0 section to CHANGELOG.md, and bumps the version in package.json. It contains no source code and touches no security-sensitive surface. Every changeset marked minor or patch maps one-to-one to a CHANGELOG bullet under the matching heading, and every omitted changeset is marked none. The repository has no CODEOWNERS file, and the timeline shows no open objections from other reviewers.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. This is a mechanical release commit made by scripts/changelog.ts version.

What was reviewed:

  • All 25 minor and patch changesets that were deleted appear word for word in the 0.15.0 section, under the right heading and in filename order. Nothing is dropped or duplicated, and multi-paragraph entries are indented the same way as in 0.14.0.
  • The 8 changesets marked none are deleted with no changelog entry, which matches the script's releaseSection.
  • Some frontmatter uses tempo-wallet: or tempo-request:. Both are allowed aliases in allowedPackages, so those entries are counted correctly.
  • The version goes from 0.14.0 to 0.15.0, a minor bump, and the section date matches the date of the release commit.
Extended reasoning...

The change bumps the version in package.json, adds the 0.15.0 section to CHANGELOG.md, and deletes the 33 pending changesets in .changelog/. No source code or build config changes. It touches no security-sensitive code. Approval rests on two checks: each changeset body matches its CHANGELOG entry exactly in the right section, and the output matches what scripts/changelog.ts produces. No CODEOWNERS file covers these paths, and the timeline shows no open objection from a human reviewer.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from 5d7449c to e0b9c72 Compare October 18, 2026 16:33

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no issues

No high-confidence issues detected in this change.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch 2 times, most recently from 2cf1cec to e30de94 Compare October 18, 2026 22:50

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no issues

No high-confidence issues detected in this change.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from e30de94 to 2056b2b Compare October 19, 2026 15:05

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no issues

No high-confidence issues detected in this change.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from 2056b2b to 10de385 Compare October 19, 2026 18:49

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no issues

No high-confidence issues detected in this change.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from 10de385 to 4e8e651 Compare October 19, 2026 23:55

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no issues

No high-confidence issues detected in this change.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from 4e8e651 to 0927bac Compare October 20, 2026 00:40

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no issues

No high-confidence issues detected in this change.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch 2 times, most recently from 3477f2a to fbc8c1e Compare October 20, 2026 23:41

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no issues

No high-confidence issues detected in this change.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from fbc8c1e to 55d37c7 Compare October 21, 2026 01:05

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no issues

No high-confidence issues detected in this change.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch 2 times, most recently from f2ee971 to 6a163ff Compare October 22, 2026 01:48

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no issues

No high-confidence issues detected in this change.

@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from 6a163ff to f9de724 Compare October 22, 2026 20:50
@tempo-github-sts
tempo-github-sts Bot force-pushed the changelog-release/main branch from f9de724 to f2c7fb1 Compare October 23, 2026 08:56

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code review found no issues

No high-confidence issues detected in this change.

@brendanjryan

Copy link
Copy Markdown
Contributor

+1

@tempo-voight-kampff tempo-voight-kampff Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Approving on behalf of @brendanjryan, who approved this pull request (head f2c7fb1d0458) with a +1 comment via Voight-Kampff.

GitHub branch protection considers pull request reviews, not +1 comments. Voight-Kampff is recording this approval on the reviewer's behalf so branch protection requirements are met.

@brendanjryan
brendanjryan merged commit 62d30c9 into main Oct 23, 2026
28 checks passed
@brendanjryan
brendanjryan deleted the changelog-release/main branch October 23, 2026 22:46
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.

2 participants