Skip to content

Release New Version#1727

Open
github-actions[bot] wants to merge 1 commit intomainfrom
changeset-release/main
Open

Release New Version#1727
github-actions[bot] wants to merge 1 commit intomainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 5, 2026

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@namehash/ens-referrals@1.7.0

Patch Changes

  • Updated dependencies []:
    • @ensnode/ensnode-sdk@1.7.0

@ensnode/ensnode-react@1.7.0

Patch Changes

  • Updated dependencies []:
    • @ensnode/ensnode-sdk@1.7.0

@ensnode/ensnode-sdk@1.7.0

Patch Changes

  • Updated dependencies []:
    • @ensnode/datasources@1.7.0

@namehash/namehash-ui@1.7.0

Patch Changes

  • Updated dependencies []:
    • @ensnode/datasources@1.7.0
    • @ensnode/ensnode-react@1.7.0
    • @ensnode/ensnode-sdk@1.7.0

@ensnode/datasources@1.7.0

@ensnode/ensnode-schema@1.7.0

@ensnode/ensrainbow-sdk@1.7.0

@ensnode/ponder-sdk@1.7.0

@ensnode/ponder-subgraph@1.7.0

ensapi@1.7.0

Minor Changes

  • #1719 4cb6dee Thanks @shrugs! - ENSNode GraphQL API: BREAKING: Removed ENSv1Domain.children in favor of Domain.subdomains.

  • #1719 4cb6dee Thanks @shrugs! - ENSNode GraphQL API: Introduce *Connection.totalCount for all *Connection fields, following the Relay specification.

  • #1719 4cb6dee Thanks @shrugs! - ENSNode GraphQL API: BREAKING: Removed Domain.subdomainCount in favor of Domain.subdomains.totalCount.

Patch Changes

  • Updated dependencies []:
    • @ensnode/datasources@1.7.0
    • @ensnode/ensnode-schema@1.7.0
    • @ensnode/ensnode-sdk@1.7.0
    • @ensnode/ponder-subgraph@1.7.0
    • @namehash/ens-referrals@1.7.0

ensadmin@1.7.0

Patch Changes

  • Updated dependencies []:
    • @ensnode/datasources@1.7.0
    • @ensnode/ensnode-schema@1.7.0
    • @ensnode/ensnode-react@1.7.0
    • @ensnode/ensnode-sdk@1.7.0
    • @namehash/namehash-ui@1.7.0

ensindexer@1.7.0

Patch Changes

  • Updated dependencies []:
    • @ensnode/datasources@1.7.0
    • @ensnode/ensrainbow-sdk@1.7.0
    • @ensnode/ensnode-schema@1.7.0
    • @ensnode/ensnode-sdk@1.7.0
    • @ensnode/ponder-sdk@1.7.0

ensrainbow@1.7.0

Patch Changes

  • Updated dependencies []:
    • @ensnode/ensrainbow-sdk@1.7.0
    • @ensnode/ensnode-sdk@1.7.0

fallback-ensapi@1.7.0

Patch Changes

  • Updated dependencies []:
    • @ensnode/datasources@1.7.0
    • @ensnode/ensnode-sdk@1.7.0

@docs/mintlify@1.7.0

@docs/ensnode@1.7.0

@docs/ensrainbow@1.7.0

@ensnode/shared-configs@1.7.0

@github-actions github-actions bot requested a review from a team as a code owner March 5, 2026 20:27
@vercel
Copy link
Contributor

vercel bot commented Mar 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
admin.ensnode.io Ready Ready Preview, Comment Mar 5, 2026 8:29pm
ensnode.io Ready Ready Preview, Comment Mar 5, 2026 8:29pm
ensrainbow.io Ready Ready Preview, Comment Mar 5, 2026 8:29pm

Releases:
  ensapi@1.7.0
  ensindexer@1.7.0
  ensadmin@1.7.0
  ensrainbow@1.7.0
  fallback-ensapi@1.7.0
  @ensnode/datasources@1.7.0
  @ensnode/ensrainbow-sdk@1.7.0
  @ensnode/ensnode-schema@1.7.0
  @ensnode/ensnode-react@1.7.0
  @ensnode/ensnode-sdk@1.7.0
  @ensnode/ponder-sdk@1.7.0
  @ensnode/ponder-subgraph@1.7.0
  @ensnode/shared-configs@1.7.0
  @docs/ensnode@1.7.0
  @docs/ensrainbow@1.7.0
  @docs/mintlify@1.7.0
  @namehash/ens-referrals@1.7.0
  @namehash/namehash-ui@1.7.0

[skip ci]
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Mar 5, 2026

Greptile Summary

This is an automated Changesets release PR that bumps all packages in the monorepo from 1.6.0 to 1.7.0, consuming three pending changesets and updating all corresponding CHANGELOG.md files. The most significant functional change is in ensapi, which introduces two breaking GraphQL API removals (ENSv1Domain.children and Domain.subdomainCount) alongside a new *Connection.totalCount field following the Relay specification.

Key changes:

  • All 19 packages/apps bumped from 1.6.01.7.0
  • Three changeset files consumed and deleted
  • ensapi CHANGELOG documents two BREAKING API removals and one new feature
  • All other packages are dependency-cascade bumps with no direct changes

Issue found:

  • The two breaking changes in ensapi (ENSv1Domain.children removal and Domain.subdomainCount removal) were classified as minor in their respective changeset files rather than major, resulting in a minor version bump (1.7.0) instead of what strict semver would require (2.0.0). Consumers may not anticipate breaking changes in a minor release.

Confidence Score: 3/5

  • Safe to merge mechanically, but the semver classification of breaking API changes as "minor" may surprise downstream consumers.
  • The release automation is correct and all version bumps are consistent. However, two explicitly BREAKING API removals in ensapi were classified as "minor" rather than "major" in the original changesets, resulting in a 1.7.0 release instead of 2.0.0. This is a process/policy concern rather than a code defect, but it does carry real risk for downstream API consumers who rely on semver to gauge breaking change exposure.
  • Pay close attention to apps/ensapi/CHANGELOG.md and the deleted changeset files .changeset/eager-parrots-follow.md and .changeset/shiny-cameras-judge.md — the breaking change classification warrants a deliberate decision before merging.

Important Files Changed

Filename Overview
apps/ensapi/CHANGELOG.md CHANGELOG correctly documents breaking changes in 1.7.0, but those breaking changes were classified as "minor" (not "major") in the original changesets, resulting in a minor version bump despite API removals.
apps/ensapi/package.json Version bumped 1.6.0 → 1.7.0; arguable whether breaking API changes should have prompted a major bump instead.
.changeset/eager-parrots-follow.md Deleted changeset that classified a BREAKING removal as "minor" — root cause of the under-versioned bump.
.changeset/shiny-cameras-judge.md Deleted changeset that classified a second BREAKING removal as "minor" — root cause of the under-versioned bump.
.changeset/neat-signs-sort.md Deleted changeset for new totalCount feature on *Connection types — correctly classified as "minor".
apps/ensadmin/package.json Version bumped 1.6.0 → 1.7.0 as expected for a dependency-only patch release.
apps/ensindexer/package.json Version bumped 1.6.0 → 1.7.0 as expected for a dependency-only patch release.
apps/ensrainbow/package.json Version bumped 1.6.0 → 1.7.0 as expected for a dependency-only patch release.
packages/datasources/package.json Version bumped 1.6.0 → 1.7.0 with no functional changes.
packages/ensnode-sdk/package.json Version bumped 1.6.0 → 1.7.0 with only transitive dependency update.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["ensapi@1.7.0\n(minor: 2 BREAKING + 1 new feature)"] --> B["@ensnode/datasources@1.7.0"]
    A --> C["@ensnode/ensnode-schema@1.7.0"]
    A --> D["@ensnode/ensnode-sdk@1.7.0"]
    A --> E["@ensnode/ponder-subgraph@1.7.0"]
    A --> F["@namehash/ens-referrals@1.7.0"]

    D --> B

    G["ensadmin@1.7.0\n(patch: dep bump)"] --> B
    G --> C
    G --> H["@ensnode/ensnode-react@1.7.0"]
    G --> D
    G --> I["@namehash/namehash-ui@1.7.0"]

    H --> D
    I --> B
    I --> H
    I --> D

    J["ensindexer@1.7.0\n(patch: dep bump)"] --> B
    J --> K["@ensnode/ensrainbow-sdk@1.7.0"]
    J --> C
    J --> D
    J --> L["@ensnode/ponder-sdk@1.7.0"]

    M["ensrainbow@1.7.0\n(patch: dep bump)"] --> K
    M --> D

    N["fallback-ensapi@1.7.0\n(patch: dep bump)"] --> B
    N --> D

    style A fill:#f96,stroke:#c00,color:#000
Loading

Last reviewed commit: 145d586

Comment on lines +7 to +12
- [#1719](https://github.com/namehash/ensnode/pull/1719) [`4cb6dee`](https://github.com/namehash/ensnode/commit/4cb6dee2a0198b630b4efdd02eb71c36c7d38025) Thanks [@shrugs](https://github.com/shrugs)! - ENSNode GraphQL API: BREAKING: Removed `ENSv1Domain.children` in favor of `Domain.subdomains`.

- [#1719](https://github.com/namehash/ensnode/pull/1719) [`4cb6dee`](https://github.com/namehash/ensnode/commit/4cb6dee2a0198b630b4efdd02eb71c36c7d38025) Thanks [@shrugs](https://github.com/shrugs)! - ENSNode GraphQL API: Introduce `*Connection.totalCount` for all `*Connection` fields, following the Relay specification.

- [#1719](https://github.com/namehash/ensnode/pull/1719) [`4cb6dee`](https://github.com/namehash/ensnode/commit/4cb6dee2a0198b630b4efdd02eb71c36c7d38025) Thanks [@shrugs](https://github.com/shrugs)! - ENSNode GraphQL API: BREAKING: Removed `Domain.subdomainCount` in favor of `Domain.subdomains.totalCount`.

Copy link
Contributor

Choose a reason for hiding this comment

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

Breaking changes versioned as minor bump

Two of the three ensapi changes in this release are explicitly labelled BREAKING:

  • Removed ENSv1Domain.children (replaced by Domain.subdomains)
  • Removed Domain.subdomainCount (replaced by Domain.subdomains.totalCount)

According to Semantic Versioning (semver), breaking/incompatible API removals should trigger a major version increment (e.g. 1.6.0 → 2.0.0), not a minor one (1.6.0 → 1.7.0). The root cause is in the now-deleted changeset files (.changeset/eager-parrots-follow.md and .changeset/shiny-cameras-judge.md), which both used "ensapi": minor instead of "ensapi": major.

Consumers relying on ENSv1Domain.children or Domain.subdomainCount may upgrade to 1.7.0 without expecting breakage, since a minor bump typically signals backwards-compatible new features. If this project intentionally deviates from strict semver (e.g. all breaking changes before a stable v2 are kept at minor), that policy should be documented clearly in the release notes.

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.

0 participants