Skip to content

fix(deps): resolve high-severity audit findings and surface them earlier - #36

Merged
ehs208 merged 2 commits into
mainfrom
fix/audit-transitive-deps
Oct 1, 2026
Merged

ehs208 merged 2 commits into
mainfrom
fix/audit-transitive-deps

Conversation

@ehs208

@ehs208 ehs208 commented Oct 1, 2026

Copy link
Copy Markdown
Owner

Description

npm audit --audit-level=high fails on main because of advisories published after #25 (fast-uri, ip-address). Every open PR that ran CI after those advisories failed on that step, dependency bumps included. Typecheck and tests passed in those runs.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • Dependency update

Changes Made

  • Refresh package-lock.json with npm audit fix (no --force). No ranges in package.json change. The result matches the lockfile change in feat: create calendars without inviting members #35 exactly, so the two PRs do not conflict.
  • CI: add a weekly schedule and workflow_dispatch trigger so a new advisory shows up on main before it blocks unrelated PRs.
  • CI: set fail-fast: false so one Node version failing no longer cancels the other two. Before this change, failures showed up as CANCELLED, which hid the actual cause.
  • Required checks (verify (18/20/22)) are unchanged.

Testing

  • npm ci, npm run typecheck, npm test (11/11), npm run build
  • npm audit --audit-level=high exits 0. One low-severity finding remains: esbuild, dev-only, Windows dev server.

Test Environment

  • Node.js Version: local
  • Operating System: macOS

🤖 Generated with Claude Code

ehs208 and others added 2 commits October 1, 2026 20:29
Resolves fast-uri and ip-address (high) plus hono, @hono/node-server,
body-parser and qs advisories via npm audit fix. No direct dependency
ranges change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A newly published advisory used to surface only when the next PR ran,
turning every open PR red at once. A weekly scheduled run reports it on
main first, and fail-fast: false keeps one Node version's failure from
hiding the results of the others.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ehs208
ehs208 merged commit 12fd311 into main Oct 1, 2026
3 checks passed
ehs208 added a commit to daylight55/TimeTree-MCP that referenced this pull request Oct 1, 2026
Picks up the lockfile refresh from ehs208#36 so this PR no longer carries it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ehs208 added a commit to daylight55/TimeTree-MCP that referenced this pull request Oct 1, 2026
Add the missing Korean README entries, use a distinct emoji from
Create Events, list calendar creation in the project guide, and drop the
Security changelog entry now that ehs208#36 ships the lockfile refresh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ehs208 added a commit that referenced this pull request Oct 7, 2026
* feat: add calendar creation without member invitations

* docs: sync create_calendar docs across READMEs

Add the missing Korean README entries, use a distinct emoji from
Create Events, list calendar creation in the project guide, and drop the
Security changelog entry now that #36 ships the lockfile refresh.

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

* fix: address calendar creation review feedback

* fix: include calendar creation in desktop extension manifest

* fix: harden calendar creation failure handling

---------

Co-authored-by: EunHyunsu <ehs208@naver.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant