chore: add v1.0.3 changelog and bump version

[qianzhicheng95]

Change-Id: I4201689c6190786822f9bd8fec43532279e4e0c1

Summary

Changes

• Change 1
• Change 2

Test Plan

• Unit tests pass
• Manual local verification confirms the lark xxx command works as expected

Related Issues

• None

Summary by CodeRabbit

• New Features - New capabilities and functionality have been added
• Bug Fixes - Critical issues have been resolved
• Documentation - Documentation has been expanded and improved
• Chores - CI pipeline and infrastructure enhancements

Version 1.0.3 is now available.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f238eb17-92be-405e-a77e-d0e75e97ae81

📥 Commits

Reviewing files that changed from the base of the PR and between bf537f8 and d21dc13.

📒 Files selected for processing (2)

• CHANGELOG.md
• package.json

---

📝 Walkthrough

Walkthrough

This PR updates the project version from 1.0.2 to 1.0.3 by bumping the package.json version number and adding a corresponding v1.0.3 changelog entry with categorized release notes.

Changes

Cohort / File(s)	Summary
Release Documentation CHANGELOG.md	Added v1.0.3 changelog entry (dated 2026-04-02) with categorized new features, bug fixes, documentation updates, and CI changes; added link reference for v1.0.3.
Package Manifest package.json	Bumped package version from 1.0.2 to 1.0.3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: add v1.0.2 changelog and bump version #192 — Follows the same release pattern: adding a changelog entry and bumping package.json version (v1.0.2).
• docs: add v1.0.1 changelog #150 — Follows the same release pattern: adding a changelog entry and bumping package.json version (v1.0.1).

Suggested labels

size/M

Suggested reviewers

• liangshuo-1
• liuxinyanglxy

Poem

🐰 A version hops from two to three,
The changelog grows, for all to see,
Release notes bloom in ordered rows,
Each feature fixed, each fix that shows! 🚀

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description contains the required template sections but lacks substantive content; the Summary and Changes sections are empty or use placeholder text instead of actual details about the version bump and changelog additions.	Fill in the Summary section with the motivation for v1.0.3, and replace placeholder text in Changes with the actual changelog entries and version bump details.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main changes: adding a v1.0.3 changelog entry and bumping the version number, which aligns with the file modifications in CHANGELOG.md and package.json.
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 feat/version103

---

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

[greptile-apps]

Greptile Summary

This PR bumps the package version from 1.0.2 to 1.0.3 in package.json and adds the corresponding v1.0.3 changelog section to CHANGELOG.md. The changes are purely administrative — no functional code is modified. The changelog entry follows the established format used by previous releases and references the correct GitHub release tag URL.

Key observations:

• Version bump in package.json is consistent with the new changelog section.
• Two PR references in CHANGELOG.md (#101 and #142) have unexpectedly low numbers relative to the rest of the v1.0.3 entries (which range from #180 to #228), and their numbers overlap with the range of earlier released versions. These may be misattributed or late-merged PRs — worth verifying.
• The PR description template was not filled in (still contains placeholder text "Change 1", "Change 2"), though this is a minor process concern for a chore PR.

Confidence Score: 5/5

Safe to merge — only changelog and version bump, no functional code changes.

The PR touches only two files: a documentation file (CHANGELOG.md) and a metadata file (package.json). Neither change affects runtime behavior. The version bump is internally consistent with the changelog. The flagged PR-number anomalies are documentation accuracy concerns, not merge blockers.

CHANGELOG.md — verify that PR references #101 and #142 are correctly attributed to v1.0.3 and not an earlier release.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds v1.0.3 changelog section with features, bug fixes, docs, and CI entries; two PR references (#101, #142) have unexpectedly low numbers relative to their listed version
package.json	Version bumped from 1.0.2 to 1.0.3, consistent with the new changelog entry

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR #231 merged] --> B[package.json version\n1.0.2 → 1.0.3]
    A --> C[CHANGELOG.md updated]
    C --> D[v1.0.3 section added\nFeatures / Bug Fixes /\nDocs / CI entries]
    C --> E[v1.0.3 reference link added\nat bottom of file]
    B --> F[npm publish @larksuite/cli@1.0.3]

Loading

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

[github-actions]

🚀 PR Preview Install Guide

🧰 CLI update

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

🧩 Skill update

npx skills add larksuite/cli#feat/version103 -y -g