chore(deps): bump gitsheets to ^1.2.0#55
Merged
Conversation
Updates the explicit range in apps/api/package.json to ^1.2.0 (was ^1.0.3, which already permitted 1.x.y resolution but pinned the lockfile to a specific 1.0.x build). Implicitly tested against 1.1.x and 1.2.x via npm install resolution across every plan in this session — explicit bump lets future readers see the intended floor. What 1.0.5 / 1.1.0 / 1.2.0 added (release notes for context, no code changes here): - 1.0.5: PushDaemon non-FF detection + startup-backlog; Sheet.query AbortSignal support. Both are forward-useful but not yet wired into our codebase — tracked in #34 (AbortSignal) and #37 (startPushDaemon wiring with NFF discrimination). - 1.1.0: Sheet.diffFrom, Sheet.attachments iterator + deleteAttachment, Repository.openSheet({prefix}), CLI buildout. The new attachment APIs matter for the deferred avatar route — tracked in #32. - 1.2.0: Content-typed records (markdown + frontmatter), lazy body loading, pluggable format module. Tracked in #44 (broad migration) and #45 (blog-post revival). `npm install` regenerates package-lock.json to pin gitsheets@1.2.0 and its new transitives (rfc6902, csv-parse, csv-stringify, markdownlint). Co-Authored-By: Claude Opus 4.7 (1M context) <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
1 participant
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.
Summary
Updates the explicit range in
apps/api/package.jsonfrom^1.0.3to^1.2.0. The previous range already permitted1.x.yresolution but the lockfile was pinned to a specific1.0.xbuild. Implicitly tested against 1.1.x and 1.2.x vianpm installresolution across every plan in this session — explicit bump lets future readers see the intended floor.What's in 1.0.x → 1.2.0 (already-tracked follow-ups)
Sheet.queryAbortSignal. Tracked in read-api: pass request.signal into Sheet.query/queryFirst/queryAll for client-disconnect cancellation #34 (AbortSignal threading) and Wire startPushDaemon() in API boot so commits actually propagate to the data remote #37 (startPushDaemon()wiring with NFF discrimination).Sheet.diffFrom,Sheet.attachmentsiterator,Sheet.deleteAttachment/deleteAttachments,Repository.openSheet({ prefix }), CLI buildout (--format,--patch,gitsheets init/edit/infer/migrate-config). The new attachment APIs matter for the deferred avatar route — tracked in write-api: implement POST /api/people/:slug/avatar (multipart attachment + image resize) #32.npm installregeneratedpackage-lock.jsonto pingitsheets@1.2.0and pull in the new transitives (rfc6902,csv-parse,csv-stringify,markdownlint).Test plan
npm run lintcleannpm run type-checkcleannpm test— 213 api + 30 web + 52 shared, all green🤖 Generated with Claude Code