Release New Version#2156
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Greptile SummaryThis is an automated Changesets release PR bumping all packages in the monorepo from
Confidence Score: 5/5This is a standard automated Changesets release PR — all changes are version bumps, CHANGELOG entries, Docker tag updates, and removal of consumed changeset files. No runtime logic is modified here. Every file changed is either a package.json version bump, a generated CHANGELOG entry, a Docker Compose image tag update, or an OpenAPI spec version field. The actual feature code lives in source PRs already merged to main; this PR only records their versions and updates manifests. apps/ensadmin/package.json and docs/ensnode.io/package.json both pin @ensnode/ensnode-sdk and enssdk to 1.15.0 rather than workspace:*, continuing a pre-existing pattern for these two packages. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
CS[Changesets Action\nOpens Release PR] --> VB[Bump all packages\n1.14.0 to 1.15.0]
VB --> CL[Update CHANGELOGs]
VB --> DK[Update Docker image tags]
VB --> OA[Update OpenAPI spec version]
VB --> RM[Remove consumed changeset files]
subgraph features [Features in 1.15.0]
F1[enssdk: beautifyInterpretedLabel\nBeautifiedLabel branded type]
F2[ensapi: BeautifiedName and BeautifiedLabel\nGraphQL scalars plus canonical filter fix]
F3[ensdb-sdk: 3 new btree indexes\nfor subdomain and domain-listing performance]
end
CL --> features
Reviews (8): Last reviewed commit: "chore(release): version apps" | Re-trigger Greptile |
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
4004c5e to
10555d7
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
10555d7 to
52815b7
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
52815b7 to
57198df
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
57198df to
a6d48d9
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
a6d48d9 to
827fea5
Compare
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| "@ensnode/ensnode-sdk": "1.15.0", | ||
| "@ensnode/scalar-react": "workspace:*", | ||
| "enssdk": "0.0.0-preview-fix-sha-89c022b-20260519094840", | ||
| "enssdk": "1.15.0", |
There was a problem hiding this comment.
@ensnode/ensnode-sdk and enssdk are pinned to 1.15.0 rather than workspace:*, unlike every other internal dependency in this file and unlike how these same packages are referenced in apps/ensapi/package.json and apps/ensindexer/package.json. This means local workspace builds must rely on a published npm version of these packages, and every future Changesets release will need to re-bump these entries. If the packages haven't been published to npm yet when a Docker image build runs, the install will fail. Was this intentional? The previous value was a preview-pinned version, which suggests this app was previously configured to consume published preview builds. Should these be switched to workspace:* to align with the other apps?
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
827fea5 to
5218462
Compare
Releases: ensapi@1.15.0 enssdk@1.15.0 @ensnode/ensdb-sdk@1.15.0 ensindexer@1.15.0 ensrainbow@1.15.0 @ensnode/datasources@1.15.0 @namehash/ens-referrals@1.15.0 enskit@1.15.0 @ensnode/ensnode-sdk@1.15.0 @ensnode/ensrainbow-sdk@1.15.0 @namehash/namehash-ui@1.15.0 @ensnode/integration-test-env@1.15.0 ensadmin@1.15.0 fallback-ensapi@1.15.0 @docs/ensnode@1.15.0 @docs/ensrainbow@1.15.0 enscli@1.15.0 ensskills@1.15.0 @ensnode/ponder-sdk@1.15.0 @ensnode/ponder-subgraph@1.15.0 @ensnode/shared-configs@1.15.0 @ensnode/ensindexer-perf-testing@1.15.0 [skip ci]
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
5218462 to
c20b813
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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
enssdk@1.15.0
Minor Changes
9c40ef1Thanks @shrugs! - AddbeautifyInterpretedLabel, which beautifies a singleInterpretedLabelper ENSIP-15, preserving Encoded LabelHashes verbatim, and returns the newBeautifiedLabelbranded type.beautifyInterpretedNameis now defined in terms ofbeautifyInterpretedLabel.@ensnode/datasources@1.15.0
Patch Changes
9c40ef1]:@namehash/ens-referrals@1.15.0
Patch Changes
9c40ef1]:@ensnode/ensdb-sdk@1.15.0
Patch Changes
#2155
addfba6Thanks @shrugs! - Add three btree indexes to the indexer schema to fix slowDomain.subdomains,get-domain-by-interpreted-name, andQuery.domainspaths:domain_resolver_relations(domain_id)— secondary lookup off the PK so the namegraph-walk CTE can left-join bydomain_idalone.domains(registry_id, label_hash)— composite (replaces the standaloneregistry_idindex, which it subsumes via leading-column prefix).domains(registry_id, left(canonical_name, 256), id)— expression composite for registry-scopedWHERE registry_id = X ORDER BY canonical_name LIMIT N(theDomain.subdomainsshape). The 256-char prefix bounds the index tuple under btree's per-tuple max; NAME-ordered queries must sort by the sameleft(...)expression for the planner to use this index for ordered scan.Updated dependencies [
9c40ef1]:enskit@1.15.0
Patch Changes
9c40ef1]:@ensnode/ensnode-sdk@1.15.0
Patch Changes
9c40ef1]:@ensnode/ensrainbow-sdk@1.15.0
Patch Changes
9c40ef1]:@namehash/namehash-ui@1.15.0
Patch Changes
9c40ef1]:enscli@1.15.0
ensskills@1.15.0
@ensnode/ponder-sdk@1.15.0
@ensnode/ponder-subgraph@1.15.0
ensapi@1.15.0
Minor Changes
9c40ef1Thanks @shrugs! - Omnigraph: addBeautifiedNameandBeautifiedLabelscalars, aCanonicalName.beautified: BeautifiedName!field, and aLabel.beautified: BeautifiedLabel!field. These expose the Name/Label beautified per ENSIP-15 for display — continue usinginterpretedfor navigation targets and lookup keys.Patch Changes
#2155
addfba6Thanks @shrugs! - Omnigraph:AccountDomainsWhereInput.canonicalnow filters on bothtrueandfalse(previouslyfalsewas a no-op). ThedefaultValue: falseis dropped — clients omittingcanonicalwill receive all Domains owned by the Account regardless of canonicality. Passcanonical: truefor canonical-only orcanonical: falsefor non-canonical-only. The underlyingDomainsWhere.canonicalinresolveFindDomainswas generalized sotypeof === "boolean"triggers the filter;null/undefinedis "no filter".Updated dependencies [
9c40ef1,addfba6]:ensadmin@1.15.0
Patch Changes
9c40ef1]:ensindexer@1.15.0
Patch Changes
#2155
addfba6Thanks @shrugs! - Basenames and Lineanames are now correctly canonicalized in theunigraphplugin.Updated dependencies [
9c40ef1,addfba6]:ensrainbow@1.15.0
Patch Changes
9c40ef1]:fallback-ensapi@1.15.0
Patch Changes
@docs/ensnode@1.15.0
Patch Changes
9c40ef1]:@docs/ensrainbow@1.15.0
Patch Changes
@ensnode/integration-test-env@1.15.0
Patch Changes
addfba6]:@ensnode/ensindexer-perf-testing@1.15.0
@ensnode/shared-configs@1.15.0