Skip to content

chore(main): release mcp-evernote 2.0.0 - #39

Merged
jack-arturo merged 1 commit into
mainfrom
release-please--branches--main--components--mcp-evernote
Aug 12, 2026
Merged

chore(main): release mcp-evernote 2.0.0#39
jack-arturo merged 1 commit into
mainfrom
release-please--branches--main--components--mcp-evernote

Conversation

@github-actions

@github-actions github-actions Bot commented May 22, 2026 •
edited by jack-arturo
Loading

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

2.0.0 (2026-08-12)

⚠ BREAKING CHANGES

  • get_resource now defaults to text extraction, not binary download; pass as:"binary" (or deprecated includeData:true) for base64. evernote_get_resource_text, evernote_get_resource_recognition, and evernote_list_note_resources are removed from the default surface (still callable as deprecated aliases; EVERNOTE_LEGACY_TOOLS=true re-lists them).
  • notes: minimum supported Node.js is now 20.16.0 (was 18.18.0), required by the pdf-parse dependency.

Features

  • api: rate-limit aware NoteStore transport (#58) (e58d66e)
  • consolidate MCP tool surface (27 → 15) behind backward-compatible aliases (#62) (d5a04fa)
  • inject live notebook names into tool descriptions and add graceful fallback (#45) (9d0a814)
  • notes: batch get_note, format projection, and paged search content (#59) (1b9a974)
  • notes: cache notebooks/tags, enrich get_note, surface rateLimitDuration (#54) (3a0272e)
  • notes: extract OCR text from image attachments (#55) (7452a51)
  • notes: extract PDF attachment text via lazy-loaded pdf-parse (#53) (00cdd0c)
  • notes: USN-keyed note body cache (#60) (2c79e2b)

Bug Fixes

  • declare the disjoint Node range pdf-parse actually supports (#71) (4976b71)
  • exit orphaned stdio MCP servers on parent death (#67) (a11e33b)
  • polling: use filtered Evernote sync chunks (#37) (46c4ec7)
  • resolve noteStoreUrl via getUserUrls() instead of non-existent getNoteStoreUrl() (#42) (c696ecb)
  • stdio: keep Evernote Thrift errors off MCP stdout (#64) (c3aeec9)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--mcp-evernote branch from 67c39e1 to 278ba56 Compare June 6, 2026 11:40
@github-actions github-actions Bot changed the title chore(main): release mcp-evernote 1.2.4 chore(main): release mcp-evernote 1.3.0 Jun 15, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--mcp-evernote branch from 278ba56 to 3c1a7f8 Compare June 15, 2026 12:03
@github-actions github-actions Bot changed the title chore(main): release mcp-evernote 1.3.0 chore(main): release mcp-evernote 2.0.0 Jun 18, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--mcp-evernote branch from 3c1a7f8 to 2fada11 Compare June 18, 2026 10:12
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--mcp-evernote branch 7 times, most recently from 10a222a to c0605cc Compare July 7, 2026 16:18
@autojack-bot autojack-bot Bot mentioned this pull request Jul 7, 2026
Closed
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--mcp-evernote branch from c0605cc to aac2092 Compare July 18, 2026 16:09
@jack-arturo jack-arturo mentioned this pull request Aug 10, 2026
Merged
jack-arturo added a commit that referenced this pull request Aug 10, 2026
@jack-arturo @claude
ci: authenticate release-please with a PAT so release PRs run CI
9f34d6b 
Release PR #39 sat unmergeable for seven months. The org ruleset requires
the `test` status check, but release-please-action authored its PR with
the default GITHUB_TOKEN, and GitHub suppresses workflow triggers for
GITHUB_TOKEN-authored events. ci.yml therefore never ran on the release
branch — check-runs on its head SHA returned total_count 0 — so the
required check could never appear and the PR could never merge.

Passing the org-level RELEASE_PLEASE_TOKEN makes release PRs trigger CI
like any other PR. Adding a push/pull_request trigger for
release-please--* branches would not work; only workflow_dispatch and
repository_dispatch escape the suppression.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jack-arturo added a commit that referenced this pull request Aug 12, 2026
@jack-arturo @claude
chore: prepare 2.0.0 release (#70)
6ded94a 
* chore: prepare 2.0.0 release

Packaging, version-reporting, and doc fixes that must land on main before
the release PR merges — npm-publish checks out main at the release commit,
so none of this can ride in the release PR itself.

Packaging (the blocker): package.json had no `files` array and there is no
.npmignore, so npm fell back to .gitignore. `npm pack` produced 153 files /
943kB including all of src/, all 33 test files, .github/, and
.claude/settings.local.json. Adding an explicit allowlist brings that to
80 files / 482kB. It also removes the latent hazard that .gitignore's
`dist/` entry could someday publish a package with no runtime code.

Version reporting: src/index.ts hardcoded "1.2.0" in the MCP Server
constructor (what every client sees in the initialize handshake) and
"1.2.3" in the connection status payload. Both are now 2.0.0 and carry
x-release-please-version annotations, with src/index.ts registered as a
generic extra-file so future releases stay in sync.

CI: add 24.x to the test matrix. The npm-publish job runs `npm test` on
Node 24, so a Node-24-only failure would otherwise surface as a git tag
and GitHub Release with no npm publish.

Docs: README gains a Node >=20.16.0 requirement (previously mentioned
nowhere), a 1.x upgrade note, and sections for the four undocumented
tools — most importantly evernote_get_resource, whose binary→text default
flip is the headline runtime break. Fixes the contributing instruction
that told people to target `develop`. CONNECTION_TROUBLESHOOTING.md, which
README links twice, presented ten retired tool names as the current API;
those now use evernote_connection({action}).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix: use string form for the generic extra-file entry

release-please's config schema only allows json/toml/yaml/xml in the
object form of extra-files. `{"type": "generic", ...}` would have failed
validation and broken the release-please run outright — generic files
must be given as a plain path string.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* ci: authenticate release-please with a PAT so release PRs run CI

Release PR #39 sat unmergeable for seven months. The org ruleset requires
the `test` status check, but release-please-action authored its PR with
the default GITHUB_TOKEN, and GitHub suppresses workflow triggers for
GITHUB_TOKEN-authored events. ci.yml therefore never ran on the release
branch — check-runs on its head SHA returned total_count 0 — so the
required check could never appear and the PR could never merge.

Passing the org-level RELEASE_PLEASE_TOKEN makes release PRs trigger CI
like any other PR. Adding a push/pull_request trigger for
release-please--* branches would not work; only workflow_dispatch and
repository_dispatch escape the suppression.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
@jack-arturo
jack-arturo force-pushed the release-please--branches--main--components--mcp-evernote branch from aac2092 to f3797ca Compare August 12, 2026 01:00
@jack-arturo
jack-arturo force-pushed the release-please--branches--main--components--mcp-evernote branch from f3797ca to 2d7c79d Compare August 12, 2026 01:08
@jack-arturo
jack-arturo merged commit 39891a1 into main Aug 12, 2026
15 checks passed
@jack-arturo
jack-arturo deleted the release-please--branches--main--components--mcp-evernote branch August 12, 2026 01:12
@jack-arturo

jack-arturo commented Aug 12, 2026

Copy link
Copy Markdown
Member

🤖 Created releases:

🌻

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

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: tagged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jack-arturo