Repository navigation
build(deps): weekly bumps from #58 without the postal-mime downgrade - #73
Merged
Merged
Conversation
Applies the npm-dependencies group bumps from Dependabot #58 (vitest, @modelcontextprotocol/sdk, @types/node, @tiptap/*, chrono-node, happy-dom 21, vite 8.3.4) but keeps postal-mime at 4.0.11, which #58 downgraded to 4.0.8. vite 8.3.4 resolves Dependabot alert #23. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes #58. It applies the same npm-dependencies group bumps, except postal-mime, which #58 downgrades from 4.0.11 to 4.0.8. This PR keeps postal-mime at 4.0.11 (the current
lateston npm, already on main since the inbound email work).Bumps
postal-mime stays at 4.0.11 (range
^4.0.5unchanged).vite 8.3.4 fixes Dependabot alert #23.
Why not #58 as-is
#58's lockfile resolves postal-mime to 4.0.8. All of 4.0.8 through 4.0.11 are a few days old, none are deprecated, and the repo's pnpm settings (pnpm 11's default release-age gate, with only a
minimumReleaseAgeExcludelist inpnpm-workspace.yaml) don't explain it, so it looks like a Dependabot resolver quirk rather than a repo setting.Tests (local, pnpm 11.12.0)
pnpm install --frozen-lockfile: okpnpm typecheck: okpnpm -r test: 1,061 tests pass (core 415, api 476, web 107, importer 63); happy-dom 21 needed no code changespnpm --filter @flow/web buildandbuild:demo: ok🤖 Generated with Claude Code