Release New Version#2156
Open
github-actions[bot] wants to merge 2 commits into
Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Greptile SummaryThis is an automated Changesets release PR bumping all packages from
Confidence Score: 5/5Standard automated release PR — all changes are mechanical version bumps, changelog updates, and Docker tag updates generated by Changesets. Every change in this PR is auto-generated: version fields incremented from 1.14.0 to 1.15.0, changeset files deleted, changelogs appended, and Docker compose default tags updated. No application logic is modified here; the substantive code changes landed in the source PRs referenced by the changeset notes and are not part of this diff. No files require special attention — all edits are Changesets-generated version metadata. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Changesets Release Action] --> B[Consume .changeset/*.md files]
B --> C[Bump versions 1.14.0 → 1.15.0]
C --> D[Update package.json files\n55 packages & apps]
C --> E[Update CHANGELOG.md files]
C --> F[Update Docker image tags\nensadmin / ensapi / ensindexer / ensrainbow]
C --> G[Update OpenAPI spec version\ndocs/ensnode.io/ensapi-openapi.json]
subgraph Key Feature Changes
H[enssdk: beautifyInterpretedLabel]
I[ensapi: BeautifiedName/BeautifiedLabel scalars]
J[ensdb-sdk/ensindexer: 3 new btree indexes]
K[ensapi: canonical:false filter fix]
end
D --> H
D --> I
D --> J
D --> K
Reviews (12): 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
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
5218462 to
c20b813
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
c20b813 to
eae51d9
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
eae51d9 to
f998321
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
f998321 to
3db82bf
Compare
Releases: ensapi@1.15.0 enssdk@1.15.0 @ensnode/ensdb-sdk@1.15.0 ensindexer@1.15.0 @ensnode/ensnode-sdk@1.15.0 ensadmin@1.15.0 ensrainbow@1.15.0 @docs/ensnode@1.15.0 @ensnode/datasources@1.15.0 @namehash/ens-referrals@1.15.0 enskit@1.15.0 @ensnode/ensrainbow-sdk@1.15.0 @namehash/namehash-ui@1.15.0 @ensnode/integration-test-env@1.15.0 fallback-ensapi@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
3db82bf to
f60d15a
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.
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
@ensnode/ensnode-sdk@1.15.0
Minor Changes
335f072Thanks @tk-o! - Addedpeekmethod toSWRCacheclass.Patch Changes
9c40ef1]: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,335f072]:@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,335f072]:enskit@1.15.0
Patch Changes
9c40ef1]:@ensnode/ensrainbow-sdk@1.15.0
Patch Changes
9c40ef1]:@namehash/namehash-ui@1.15.0
Patch Changes
9c40ef1,335f072]: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,335f072]:ensadmin@1.15.0
Patch Changes
9c40ef1,335f072]:ensindexer@1.15.0
Patch Changes
#2155
addfba6Thanks @shrugs! - Basenames and Lineanames are now correctly canonicalized in theunigraphplugin.Updated dependencies [
9c40ef1,addfba6,335f072]:ensrainbow@1.15.0
Patch Changes
9c40ef1,335f072]:fallback-ensapi@1.15.0
Patch Changes
335f072]:@docs/ensnode@1.15.0
Patch Changes
9c40ef1,335f072]:@docs/ensrainbow@1.15.0
Patch Changes
@ensnode/integration-test-env@1.15.0
Patch Changes
addfba6,335f072]:@ensnode/ensindexer-perf-testing@1.15.0
@ensnode/shared-configs@1.15.0