chore: prepare 1.1.0 release metadata - #134
Merged
Merged
Conversation
Bump to 1.1.0 for the beacon chain client added in #132, and record the release in CHANGELOG.md. Minor rather than patch: `feat: add beacon client connector` adds public API surface. The many `fix(beacon):` commits in the range are review rounds on that same unreleased feature, so they are summarised into the feature description rather than listed as fixes to a shipped release — matching how 1.0.2 was written. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
martinssvlabs
requested review from
Chris-ssvlabs and
RaekwonIII
and removed request for
Chris-ssvlabs
August 10, 2026 15:23
RaekwonIII
enabled auto-merge
August 10, 2026 15:23
Chris-ssvlabs
approved these changes
Aug 10, 2026
RaekwonIII
approved these changes
Aug 11, 2026
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
3 participants
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.
Release metadata for
1.1.0. Same shape as #131: version bump plus a curatedCHANGELOG.mdentry, no source changes.Why 1.1.0 and not 1.0.3
feat: add beacon client connector(#132) adds public API surface — a beacon chain client onsdk.api, new exported readers, and theextendedConfig.beacon.endpointoption. That is a minor, not a patch.Why the changelog is short
The unreleased range (
v1.0.2..main) is #132 and #133. It contains onefeat, one unrelatedfix(config), onedocs, and ~21fix(beacon):commits. Those 21 are review rounds on the beacon feature before it ever shipped, so listing them as "Fixes" would describe fixes to a release that never existed. The user-visible ones — credential and query-string redaction in error messages — are folded into the feature description instead. This matches how the 1.0.2 entry was curated rather than dumped.After merge
git tag v1.1.0 <merge-sha> && git push origin v1.1.0— lightweight, matchingv1.0.2, which points at chore: prepare 1.0.2 release metadata #131's merge commit.pnpm run v-pub-tarballto check the tarball, thennpm publish.dist/is already current onmainvia #133 and carries no version string, so this bump produces no dist diff and will not open anotherci/update-artifactsPR.