Skip to content

chore: add v1.0.2 changelog and bump version#192

Merged
liangshuo-1 merged 1 commit intomainfrom
chore/changelog-v1.0.2
Apr 1, 2026
Merged

chore: add v1.0.2 changelog and bump version#192
liangshuo-1 merged 1 commit intomainfrom
chore/changelog-v1.0.2

Conversation

@liangshuo-1
Copy link
Copy Markdown
Collaborator

@liangshuo-1 liangshuo-1 commented Apr 1, 2026

Summary

  • Add CHANGELOG.md entry for v1.0.2 release
  • Bump package.json version from 1.0.1 to 1.0.2

Changelog includes

  • Features: OS keychain/DPAPI sandbox error handling, mail local image path auto-resolve
  • Bug Fixes: login --no-wait URL formatting
  • Documentation: AGENTS development guide
  • CI: PR business area labels and skill format check
  • Chore: Pull request template

Summary by CodeRabbit

  • Chores
    • Version bumped to 1.0.2.
    • Changelog updated with release information.

Change-Id: Id02603da7916689f79861f543a5e0f261f443753
@github-actions github-actions bot added the size/M Single-domain feat or fix with limited business impact label Apr 1, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 1, 2026

📝 Walkthrough

Walkthrough

The 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

Cohort / File(s) Summary
Release Management
CHANGELOG.md, package.json
Added v1.0.2 release entry with categorized updates (Features, Bug Fixes, Documentation, CI, Chore) and updated package version from 1.0.1 to 1.0.2.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop, hop, hooray! A version ascends,
From one-oh-one to one-oh-two it blends,
The changelog sings of fixes and cheer,
With features so bright, our release is here! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main changes: adding a v1.0.2 changelog entry and bumping the version number in package.json.
Description check ✅ Passed The description covers the summary and changelog contents but is missing the Test Plan and Related Issues sections from the template.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/changelog-v1.0.2

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps
Copy link
Copy Markdown

greptile-apps bot commented Apr 1, 2026

Greptile Summary

This PR is a standard release bookkeeping chore: it bumps package.json from 1.0.11.0.2 and prepends the matching CHANGELOG.md entry documenting the features, bug fixes, docs, CI, and chore changes delivered in this release.

  • CHANGELOG.md: New [v1.0.2] - 2026-04-01 section added at the correct position (above v1.0.1), following the established Keep-a-Changelog format; reference link appended at the bottom in the correct order.
  • package.json: version field updated to \"1.0.2\", consistent with the changelog entry.
  • All referenced PR numbers (#173, #139, #169, #178, #148, #176) are plausible and the entries are descriptive.
  • No logic, source, or configuration changes are included — the diff is purely metadata/documentation.

Confidence Score: 5/5

Safe 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

Filename Overview
CHANGELOG.md Adds well-formed v1.0.2 changelog entry with features, bug fixes, docs, CI, and chore sections, plus the corresponding reference link at the bottom.
package.json Single-field version bump from 1.0.1 to 1.0.2, consistent with the new CHANGELOG entry.

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"]
Loading

Reviews (1): Last reviewed commit: "chore: add v1.0.2 changelog and bump ver..." | Re-trigger Greptile

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

🧹 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.yml and internal/build/build.go, the Go CLI binary's version is set via ldflags using {{ .Version }} from git tags. After merging this PR, create a v1.0.2 git 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.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5e140515-46ff-4957-aecd-f314fc79ac57

📥 Commits

Reviewing files that changed from the base of the PR and between d4c051d and f950211.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • package.json

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

🚀 PR Preview Install Guide

🧰 CLI update

npm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@f950211745204618c99f84bba39a7f64fddd4a2e

🧩 Skill update

npx skills add larksuite/cli#chore/changelog-v1.0.2 -y -g

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Apr 1, 2026

CLA assistant check
All committers have signed the CLA.

@liangshuo-1 liangshuo-1 merged commit a703202 into main Apr 1, 2026
10 checks passed
@liangshuo-1 liangshuo-1 deleted the chore/changelog-v1.0.2 branch April 1, 2026 13:17
tuxedomm pushed a commit that referenced this pull request Apr 3, 2026
Change-Id: Id02603da7916689f79861f543a5e0f261f443753
This was referenced Apr 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/M Single-domain feat or fix with limited business impact

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants