Repository navigation
chore: release 0.15.2 - #310
tempo-github-sts[bot] wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
LGTM. This is a standard release bump to 0.15.2.
What was reviewed:
- The deleted
.changelog/release-build-once.mdchangeset text matches the new0.15.2Patch Changes entry in CHANGELOG.md word for word. - The
package.jsonversion moved from 0.15.1 to 0.15.2, and no other file in the repo still references 0.15.1.
Extended reasoning...
The change touches only CHANGELOG.md, package.json's version field and one deleted changeset file, and contains no code. It touches no security-sensitive surface. It follows the repo's changeset release pattern exactly, and the repo has no CODEOWNERS or ANTOWNERS file. The PR timeline shows no reviewer objections.
aaa0b9a to
8107af9
Compare
There was a problem hiding this comment.
LGTM. This is a standard release bump to 0.15.2.
What was reviewed:
- Both deleted
.changelog/*.mdchangesets are patch-level, and their text appears word for word under the new## 0.15.2 (2026-11-05)/### Patch Changesheading in CHANGELOG.md, in the same format as 0.15.1. - In package.json the version goes from 0.15.1 to 0.15.2, which matches two patch changesets. No other file in the repo holds the version string.
Extended reasoning...
The change touches only release metadata: it deletes two changeset files, adds a CHANGELOG.md section and bumps the version in package.json. It touches no source code or security-sensitive surface. The changelog text matches the deleted changesets exactly, and a patch bump is correct for two patch-level entries. No CODEOWNERS file covers these paths, the hunt ended with dry_streak, and the timeline shows no outstanding change requests.
8107af9 to
12c5f38
Compare
There was a problem hiding this comment.
LGTM. This is a standard release commit for 0.15.2.
What was reviewed:
- All three CHANGELOG.md entries match the deleted changesets word for word, including the new
mach-next-offerentry added in the latest push. - The patch bump from 0.15.1 to 0.15.2 in package.json is right, since all three changesets are
patch. - The
tempo-requestchangeset belongs here:.changelog/config.tomlliststempo-requestas an alias of the single sharedwallet-clipackage.
Extended reasoning...
The change deletes three pending changesets under .changelog/, moves their text into a new 0.15.2 section in CHANGELOG.md, and bumps the version in package.json. It has no source code changes and touches nothing security-sensitive. It has the same shape as the earlier 0.15.1 release commit. The repo has no CODEOWNERS file, and the timeline shows no open objections from other reviewers.
12c5f38 to
f4127d3
Compare
There was a problem hiding this comment.
LGTM. This is a mechanical release commit for 0.15.2.
What was reviewed:
- All four deleted changesets are in the new 0.15.2 section, and each entry matches its changeset word for word. No changesets are left in .changelog/.
- The
tempo-request: patchfrontmatter belongs in this changelog: .changelog/config.toml liststempo-requestas an alias of the single sharedwallet-clipackage. - The version goes from 0.15.1 to 0.15.2 in package.json, and the section heading and structure match the 0.15.1 section.
Extended reasoning...
The change only touches CHANGELOG.md, package.json and the four deleted .changelog/ changeset files. It changes no source code and touches no security-sensitive surface. Every changeset's text was moved into CHANGELOG.md word for word. The one unusual package key, tempo-request, is a configured alias of the shared wallet-cli version. There is no CODEOWNERS file and no outstanding reviewer objection in the timeline.
Version wallet-cli to 0.15.2 and update CHANGELOG.md.