Skip to content

docs: add v1.0.1 changelog#150

Merged
qianzhicheng95 merged 1 commit intomainfrom
feat/changelog101
Mar 31, 2026
Merged

docs: add v1.0.1 changelog#150
qianzhicheng95 merged 1 commit intomainfrom
feat/changelog101

Conversation

@qianzhicheng95
Copy link
Copy Markdown
Collaborator

@qianzhicheng95 qianzhicheng95 commented Mar 31, 2026

Change-Id: Ie4751db5ae19689c49deac69007516bf381233b3

Summary by CodeRabbit

  • New Features

    • Automatic update detection and notification
    • Download auto-extension support
    • Message search with automatic pagination
  • Bug Fixes

    • Multiple stability and usability improvements
  • Documentation

    • Release documentation updates
  • CI

    • Workflow enhancements and improvements

Change-Id: Ie4751db5ae19689c49deac69007516bf381233b3
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 31, 2026

📝 Walkthrough

Walkthrough

A new release version v1.0.1 changelog entry was added, documenting features including automatic update detection and message search pagination, along with bug fixes, documentation updates, and CI workflow changes. A corresponding reference link to the GitHub releases tag was also added.

Changes

Cohort / File(s) Summary
Changelog Update
CHANGELOG.md
Added v1.0.1 release entry (dated 2026-03-31) with sections for Features, Bug Fixes, Documentation, and CI. Included multiple product/CLI improvements and fixes, with a new markdown reference link [v1.0.1] pointing to the GitHub releases tag.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A changelog hops with version pride,
v1.0.1 with updates wide,
Features, fixes, docs so neat,
CI workflows all complete!
Burrow deep in release delight,
GitHub tags shine ever bright! 🌟

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: add v1.0.1 changelog' clearly and concisely describes the main change—adding a changelog entry for version 1.0.1 to the documentation.
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/changelog101

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

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Mar 31, 2026

Greptile Summary

This PR adds a v1.0.1 changelog entry to CHANGELOG.md, documenting all notable changes since the initial v1.0.0 release, including new features, bug fixes, documentation updates, and CI improvements. The entry is well-structured and follows the existing changelog format.

Key changes documented in v1.0.1:

  • New features: automatic CLI update detection, npm publish workflow, auto-extension for downloads, markdown normalization, and auto-pagination for message search
  • Bug fixes: base history read scope correction, removal of overly broad send scopes, and silent failure resolution in lark-cli api
  • Documentation: several usability and clarity improvements to READMEs and command docs
  • CI: golangci-lint integration and workflow improvements

Minor observations:

  • One documentation entry ("Clarify install methods as alternatives and add source build steps") is missing its associated PR/issue reference number, unlike all other entries in the section
  • "Remove useless files (feat:remove useless files #131)" is listed under ### Features but is more accurately a maintenance/chore task

Confidence Score: 5/5

Documentation-only change with no code impact; safe to merge.

This is a pure documentation PR that only adds a changelog entry. There is no executable code changed, no risk of regressions, and the changelog content is well-structured. The two P2 style suggestions are non-blocking.

No files require special attention.

Important Files Changed

Filename Overview
CHANGELOG.md Adds v1.0.1 changelog section with features, bug fixes, documentation, and CI entries; one documentation entry is missing an issue reference number and one feature entry may be miscategorized.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[CHANGELOG.md] --> B[v1.0.1 - 2026-03-31]
    A --> C[v1.0.0 - 2026-03-28]
    B --> D[Features]
    B --> E[Bug Fixes]
    B --> F[Documentation]
    B --> G[CI]
    D --> D1["Auto CLI update detection (#144)"]
    D --> D2["npm publish workflow (#145)"]
    D --> D3["Auto extension for downloads (#16)"]
    D --> D4["Remove useless files (#131)"]
    D --> D5["Markdown message normalization (#28)"]
    D --> D6["Auto-pagination for message search (#30)"]
    E --> E1["Base history read scope fix (#96)"]
    E --> E2["Remove sensitive send scope (#92)"]
    E --> E3["Silent failure fix in lark-cli api (#85)"]
    F --> F1["Multiple docs improvements (#11, #12, #19, #23, #26, #61, #90, #103)"]
    F --> F2["Clarify install methods (no ref)"]
    G --> G1["golangci-lint + CI workflows (#71)"]
Loading

Reviews (1): Last reviewed commit: "docs: add v1.0.1 changelog" | Re-trigger Greptile

Comment thread CHANGELOG.md
Comment thread CHANGELOG.md
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)
CHANGELOG.md (1)

32-32: Optional consistency pass for tracker references.

Line 32 is the only bullet in this block without a (#...) reference. If intentional, OK; otherwise consider adding one for consistency/auditability.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 32, The changelog entry "- Clarify install methods as
alternatives and add source build steps" is missing a tracker reference like the
other bullets; update that bullet to include the appropriate issue/PR reference
in the form "(`#1234`)" to match the rest of the block for consistency and
auditability, e.g., append the correct "(#...)" identifier for the issue or PR
that introduced this change.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@CHANGELOG.md`:
- Line 32: The changelog entry "- Clarify install methods as alternatives and
add source build steps" is missing a tracker reference like the other bullets;
update that bullet to include the appropriate issue/PR reference in the form
"(`#1234`)" to match the rest of the block for consistency and auditability, e.g.,
append the correct "(#...)" identifier for the issue or PR that introduced this
change.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d13f620b-93a4-4130-ad76-062c6e2e1bdf

📥 Commits

Reviewing files that changed from the base of the PR and between 27139a0 and 082e468.

📒 Files selected for processing (1)
  • CHANGELOG.md

@qianzhicheng95 qianzhicheng95 merged commit 8fc7e12 into main Mar 31, 2026
5 checks passed
@qianzhicheng95 qianzhicheng95 deleted the feat/changelog101 branch March 31, 2026 11:14
tuxedomm pushed a commit that referenced this pull request Apr 3, 2026
Change-Id: Ie4751db5ae19689c49deac69007516bf381233b3

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai coderabbitai Bot mentioned this pull request Apr 7, 2026
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