Skip to content

chore(main): release 0.2.0 - #5

Merged
boojack merged 2 commits into
mainfrom
release-please--branches--main--components--web-clipper
Jul 23, 2026
Merged

chore(main): release 0.2.0#5
boojack merged 2 commits into
mainfrom
release-please--branches--main--components--web-clipper

Conversation

@boojack

@boojack boojack commented Jul 20, 2026

Copy link
Copy Markdown
Member

🤖 I have created a release beep boop

0.2.0 (2026-07-23)

Features

  • connection: support direct Memos connections (1eafdaa)
  • i18n: localize extension experience (a6b029a)
  • options: add guided setup and clip templates (4f60876)
  • release: automate GitHub extension releases (e88dc96)

Bug Fixes

  • ci: exclude shadcn from production audit (73ab2d2)
  • ci: remove empty e2e job and add build config (278e86d)
  • popup: display visibility labels in title case (26fad06)
  • security: harden authentication and secret handling (1b69414)

This PR was generated with Release Please. See documentation.

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Review Change Stack

Walkthrough

The release manifest and npm package version are updated from 0.1.0 to 0.2.0. CHANGELOG.md adds a dated 0.2.0 release section with feature and improvement entries.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the versioned release update.
Description check ✅ Passed The description matches the release notes and change set.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Checkov (3.3.8)
.release-please-manifest.json

Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'

package.json

Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@boojack
boojack force-pushed the release-please--branches--main--components--web-clipper branch 2 times, most recently from 70f8450 to 4ff2e95 Compare July 23, 2026 12:35
@boojack
boojack force-pushed the release-please--branches--main--components--web-clipper branch from 4ff2e95 to 57b4754 Compare July 23, 2026 12:38

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

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)

5-16: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Align the headings with the Release Please configuration.

release-please-config.json defines Features, Bug Fixes, Performance Improvements, Dependencies, and Reverts, but this release uses What's new and Improvements. Rename these headings or update the Release Please configuration so future generated changelogs remain consistent.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` around lines 5 - 16, Align the changelog section headings with
the categories defined in release-please-config.json by renaming “What's new”
and “Improvements” to matching configured headings, or update the configuration
to use these headings consistently for future generated changelogs.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@CHANGELOG.md`:
- Around line 5-16: Align the changelog section headings with the categories
defined in release-please-config.json by renaming “What's new” and
“Improvements” to matching configured headings, or update the configuration to
use these headings consistently for future generated changelogs.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d9b113c5-ee27-4f17-a88a-65998ff41797

📥 Commits

Reviewing files that changed from the base of the PR and between 4ff2e95 and 6b49ec9.

📒 Files selected for processing (3)
  • .release-please-manifest.json
  • CHANGELOG.md
  • package.json
🚧 Files skipped from review as they are similar to previous changes (2)
  • .release-please-manifest.json
  • package.json

@boojack
boojack merged commit 7b58795 into main Jul 23, 2026
1 of 2 checks passed
@boojack

boojack commented Jul 23, 2026

Copy link
Copy Markdown
Member Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants