Skip to content

chore: 0.35.0 - #77

Merged
snakajima merged 1 commit into
mainfrom
chore/bump-0.35.0
Aug 29, 2026
Merged

chore: 0.35.0#77
snakajima merged 1 commit into
mainfrom
chore/bump-0.35.0

Conversation

@snakajima

@snakajima snakajima commented Aug 29, 2026

Copy link
Copy Markdown
Contributor

#76views[].ownRead)が版を上げずに入ったので、その分です。#74 と同じ形の bump だけの PR。

0.34.0 → 0.35.0(追加のみ、既存の宣言の投影は 1 バイトも変わらない)。

README に 1 段落

「contract の版」の節は MAJOR / MINOR / PATCH を並べたあと、uidField がなぜ 2.0.0 → 1.1.0 → 何も無しになったかを説明しています。ownReadそのどれでもないので、同じところに置きました:

A key can also be none of the three. views[].ownRead adds nothing to a projection: it changes which value an EXISTING key takes (scope, from all to own, with the selector readers have built a where from since the first release). There is nothing for an older reader to ignore, because there is nothing it has not already been reading — so the contract does not move, and the package version does.

livelimit は「古い読み手が安全に無視できる追加」でした。ownRead は追加ではなく、既存の鍵が取る値が変わるだけなので、古い読み手は知らないまま正しく narrow します。「なぜこれは minor ではないのか」を後から誰かが辿れるように書いています。

確認

yarn test 568 全緑 / yarn lint / yarn typecheck / yarn format clean。

work in mulmoterminal

Summary by Sourcery

Release version 0.35.0 to account for the existing views[].ownRead behavior without changing the projection contract.

Documentation:

  • Document why the views[].ownRead change does not alter the contract version while still requiring a package version bump.

Chores:

  • Bump the package version from 0.34.0 to 0.35.0.

#76(`views[].ownRead`)が版を上げずに入ったので、その分。

README の「contract の版」に 1 段落足した。`ownRead` は MAJOR / MINOR / PATCH の
どれでもない —— **投影に何も足さない**からで、変わるのは既存の鍵 `scope` が取る値
(`all` → `own`、選択子は最初の版から読み手が `where` を組んできたもの)。古い読み手が
無視すべきものが無い(既に読んでいるものしか無い)ので契約は動かず、パッケージの版だけが動く。
その節は `uidField` がなぜ 2.0.0 → 1.1.0 → 何も無しになったかを説明している場所なので、
「なぜこれは minor ではないのか」も同じところに置いた。

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CRe3fgJnWNLRAqrjvjpHLn

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @snakajima, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 2 hours and 39 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

@coderabbitai

coderabbitai Bot commented Aug 29, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ea2d3a66-4a31-4f77-b40c-bc1cc275797a


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sourcery-ai

sourcery-ai Bot commented Aug 29, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This release-only PR bumps the package from 0.34.0 to 0.35.0 and documents why the existing ownRead behavior warrants a package version change but does not alter the APP_PROTOCOL contract or existing projection declarations.

File-Level Changes

Change Details Files
Document the versioning rationale for views[].ownRead without changing the projection contract.
  • Explain that ownRead changes the value of the existing scope key rather than adding projection data.
  • Clarify why older readers continue to narrow correctly and why the contract version remains unchanged.
README.md
Bump the package version for the unversioned ownRead change.
  • Update the package version from 0.34.0 to 0.35.0.
package.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

@snakajima
snakajima merged commit 28eb809 into main Aug 29, 2026
8 checks passed
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