Bump version to 2.1.0 and write the changelog - #60
Merged
Conversation
snoble
force-pushed
the
claude/measure-coverage
branch
from
August 6, 2026 22:02
22a6c29 to
00f917f
Compare
snoble
force-pushed
the
claude/bump-version-2-1-0
branch
from
August 6, 2026 22:02
52564f6 to
fb5d134
Compare
snoble
force-pushed
the
claude/measure-coverage
branch
from
August 6, 2026 22:08
00f917f to
03b3692
Compare
snoble
force-pushed
the
claude/bump-version-2-1-0
branch
from
August 6, 2026 22:08
fb5d134 to
e97d42b
Compare
snoble
changed the base branch from
claude/measure-coverage
to
claude/typed-query-methods
August 6, 2026 22:08
snoble
changed the base branch from
claude/typed-query-methods
to
claude/typed-response-fields
August 6, 2026 22:21
snoble
force-pushed
the
claude/bump-version-2-1-0
branch
2 times, most recently
from
August 6, 2026 22:39
06d0060 to
8b4c727
Compare
snoble
changed the base branch from
claude/typed-response-fields
to
claude/idiomatic-batch-api
August 6, 2026 22:39
snoble
force-pushed
the
claude/bump-version-2-1-0
branch
from
August 6, 2026 22:46
8b4c727 to
199fdca
Compare
snoble
changed the base branch from
claude/idiomatic-batch-api
to
claude/test-response-types
August 6, 2026 22:46
snoble
force-pushed
the
claude/bump-version-2-1-0
branch
from
August 6, 2026 23:38
199fdca to
275960d
Compare
snoble
changed the base branch from
claude/test-response-types
to
claude/experimental-opt-in
August 6, 2026 23:38
snoble
force-pushed
the
claude/experimental-opt-in
branch
from
August 6, 2026 23:45
94c50e6 to
838dece
Compare
snoble
force-pushed
the
claude/bump-version-2-1-0
branch
2 times, most recently
from
August 6, 2026 23:57
96b5075 to
6aea00f
Compare
snoble
changed the base branch from
claude/experimental-opt-in
to
claude/lint-clean
August 6, 2026 23:57
vigneshwerv
force-pushed
the
claude/lint-clean
branch
from
August 10, 2026 19:14
4fcacd5 to
15eab26
Compare
vigneshwerv
force-pushed
the
claude/bump-version-2-1-0
branch
from
August 10, 2026 19:14
6aea00f to
8fe57b9
Compare
vigneshwerv
force-pushed
the
claude/lint-clean
branch
from
August 10, 2026 21:18
15eab26 to
1232a9e
Compare
vigneshwerv
force-pushed
the
claude/bump-version-2-1-0
branch
from
August 10, 2026 21:18
8fe57b9 to
a9d87f5
Compare
vigneshwerv
force-pushed
the
claude/lint-clean
branch
from
August 10, 2026 21:23
1232a9e to
2c07567
Compare
vigneshwerv
force-pushed
the
claude/bump-version-2-1-0
branch
from
August 10, 2026 21:23
a9d87f5 to
4d27507
Compare
vigneshwerv
force-pushed
the
claude/lint-clean
branch
from
August 10, 2026 21:39
2c07567 to
d12fd6a
Compare
vigneshwerv
force-pushed
the
claude/bump-version-2-1-0
branch
from
August 10, 2026 21:40
4d27507 to
5925875
Compare
vigneshwerv
approved these changes
Aug 10, 2026
vigneshwerv
force-pushed
the
claude/lint-clean
branch
from
August 10, 2026 22:25
d12fd6a to
820cf4c
Compare
vigneshwerv
force-pushed
the
claude/bump-version-2-1-0
branch
from
August 10, 2026 22:25
5925875 to
590bf62
Compare
vigneshwerv
force-pushed
the
claude/lint-clean
branch
from
August 10, 2026 23:18
820cf4c to
1275f7a
Compare
Minor rather than major: everything user-facing in this stack is additive. The batch method, the typed payloads, the two Tapioca compilers and `load_queries` are all new, the schema refresh only adds types, nothing was removed, and no signature narrowed. The hand-written `add_ledger_entries` wrapper cannot shadow an existing caller's method, because the operation was not in `queries.graphql` before. The one argument against, recorded in the changelog rather than left to be discovered: an unusable `oauth_url` now raises `ArgumentError` where two different exception classes came out before. Under a strict reading that is breaking. Both were constructor-time failures on a misconfigured URL rather than handled paths, so minor is the call -- but the entry says so and tells anyone rescuing `URI::InvalidURIError` what to rescue instead. No dependency versions moved. The gemspec's constraints and `required_ruby_version` are untouched, and no locked gem changed: the RBIs regenerated earlier in the stack were stale against a lockfile that was already current. Separate from the rest because this repository releases that way, and a version bump has no business inside a PR about anything else.
vigneshwerv
force-pushed
the
claude/bump-version-2-1-0
branch
from
August 10, 2026 23:20
590bf62 to
e2cff4d
Compare
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.
Top of the stack, on #63. Release artifacts only — version, changelog, and the
fragment-devline inGemfile.lockthat follows from it.Split out because this repository releases that way (
Bump version to 1.4.5,Update 2.0.0 Changelog), and a version bump has no business inside a PR about anything else.Why minor
Everything user-facing in the stack is additive: the batch method, the typed payloads, the two Tapioca compilers,
load_queries,rake coverage. Nothing removed, no signature narrowed. The hand-writtenadd_ledger_entrieswrapper cannot shadow an existing caller's method because the operation was not inqueries.graphqlbefore #54.The argument against, which the changelog states
#55 changes the exception class raised for an unusable
oauth_url:'ftp://…'NoMethodError: undefined method 'request_uri', raised later inside the token requestArgumentErrorfromFragmentClient.new'not a url'URI::InvalidURIError: bad URIArgumentErrorfromFragmentClient.newStrictly that is breaking. I think minor is right — both were constructor-time crashes on misconfiguration rather than paths anyone handles, and nobody rescues
NoMethodError. But it is a judgement call, so the changelog says so and tells anyone rescuingURI::InvalidURIErrorto rescueArgumentError. My first draft documented only the first row and silently omitted the second, which is the one someone might plausibly have caught.If you would rather ship 3.0.0 on that basis, it is a one-line change here.
No dependency versions moved
Worth saying because #56 is a 58k-line diff that looks like a dependency bump. The gemspec's constraints and
required_ruby_versionare untouched, and no locked gem changed — the lockfile already had tapioca 0.16.8, graphql 2.6.7 and activesupport 8.1.3, and only the checked-in RBIs were behind. The one addition anywhere issimplecovas a development dependency, in #59.🤖 Generated with Claude Code