chore: bump mereader to v2.7

[wu21-web]

Summary by Sourcery

Bump the mereader package to version 2.7.

Enhancements:

• Update the mereader package version from 2.6 to 2.7.

Build:

• Synchronize the package lockfile with the new package version.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
me-reader	Ready	Preview	Sep 7, 2026 9:54am UTC

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This maintenance change releases the package as version 2.7 by updating the manifest and matching lockfile metadata, with no application-code changes.

File-Level Changes

Change	Details	Files
Bump the package version from 2.6 to 2.7 and synchronize the lockfile metadata.	Update the package manifest version. Regenerate the corresponding package-lock version entries.	package.json package-lock.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="package.json" line_range="3" />
<code_context>
 {
   "name": "mereader",
-  "version": "2.6",
+  "version": "2.7",
   "lockfileVersion": 3,
   "requires": true,
</code_context>
<issue_to_address>
**issue (bug_risk):** The package version remains non-semver (`2.7` has only two numeric components), so npm versioning or publishing commands that validate `package.json` reject the release.

**Triggers:** When this package is published or versioned through npm.

**Suggested fix:** Use a valid three-component version such as `2.7.0` and keep the lockfile metadata synchronized.
</issue_to_address>

Sourcery assessment

Approval pending. 1 finding to address first.

Blocking findings: package.json:3

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[sourcery-ai]

issue (bug_risk): The package version remains non-semver (2.7 has only two numeric components), so npm versioning or publishing commands that validate package.json reject the release.

Triggers: When this package is published or versioned through npm.

Suggested fix: Use a valid three-component version such as 2.7.0 and keep the lockfile metadata synchronized.