chore: add v1.0.2 changelog and bump version#192
Conversation
Change-Id: Id02603da7916689f79861f543a5e0f261f443753
📝 WalkthroughWalkthroughThe package version was bumped from 1.0.1 to 1.0.2 in package.json, and a corresponding v1.0.2 changelog entry was added documenting features, bug fixes, documentation updates, CI changes, and chores with an associated GitHub release link reference. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Greptile SummaryThis PR is a standard release bookkeeping chore: it bumps
Confidence Score: 5/5Safe to merge — purely a version bump and changelog update with no code or configuration changes. Both changed files are documentation/metadata only. The version in package.json is consistent with the new CHANGELOG entry, the changelog format matches the established pattern, and the reference link is placed in the correct order. No P0, P1, or meaningful P2 findings. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["v1.0.0 (2026-03-28)"] --> B["v1.0.1 (2026-03-31)"]
B --> C["v1.0.2 (2026-04-01) ← this PR"]
C --> D1["#173 OS keychain/DPAPI sandbox error handling"]
C --> D2["#139 mail: auto-resolve local image paths"]
C --> D3["#169 fix login --no-wait URL formatting"]
C --> D4["#178 AGENTS development guide"]
C --> D5["#148 PR labels & skill format check CI"]
C --> D6["#176 pull request template"]
Reviews (1): Last reviewed commit: "chore: add v1.0.2 changelog and bump ver..." | Re-trigger Greptile |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
package.json (1)
3-3: Ensure git tag v1.0.2 is created for version synchronization.The npm package version (1.0.2) needs to match the git tag used by goreleaser to inject the version into the Go binary. Based on
.goreleaser.ymlandinternal/build/build.go, the Go CLI binary's version is set via ldflags using{{ .Version }}from git tags. After merging this PR, create av1.0.2git tag to ensure both the npm package and the Go binary report the same version.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` at line 3, The package.json version was bumped to "1.0.2" but the Git tag used by goreleaser to populate the Go binary version is missing; after merging, create and push a git tag named v1.0.2 so {{ .Version }} used in .goreleaser.yml (and consumed by internal/build/build.go) matches package.json's version, e.g., run git tag -a v1.0.2 -m "release v1.0.2" and push the tag to origin.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@package.json`:
- Line 3: The package.json version was bumped to "1.0.2" but the Git tag used by
goreleaser to populate the Go binary version is missing; after merging, create
and push a git tag named v1.0.2 so {{ .Version }} used in .goreleaser.yml (and
consumed by internal/build/build.go) matches package.json's version, e.g., run
git tag -a v1.0.2 -m "release v1.0.2" and push the tag to origin.
🚀 PR Preview Install Guide🧰 CLI updatenpm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@f950211745204618c99f84bba39a7f64fddd4a2e🧩 Skill updatenpx skills add larksuite/cli#chore/changelog-v1.0.2 -y -g |
Change-Id: Id02603da7916689f79861f543a5e0f261f443753
Summary
Changelog includes
--no-waitURL formattingSummary by CodeRabbit