Release New Version#2074
Open
github-actions[bot] wants to merge 2 commits intomainfrom
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 in the monorepo from
Confidence Score: 5/5This PR is safe to merge — it is an automated Changesets release commit with no logic changes. Every file change is mechanical: version strings in package.json files, Docker image default tags, the OpenAPI spec version field, CHANGELOG entries, and deletion of consumed changeset stubs. No source code, business logic, or configuration beyond version numbers was modified. All bumps are consistent at 1.12.0 across packages and services. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Changesets Action] --> B[Consume .changeset/*.md files]
B --> C[Bump versions: 1.11.1 → 1.12.0]
C --> D[Update package.json files\n~24 packages]
C --> E[Update CHANGELOG.md files\n~24 changelogs]
C --> F[Update Docker image tags\nensadmin / ensapi / ensindexer / ensrainbow]
C --> G[Update ensapi-openapi.json\ninfo.version]
D & E & F & G --> H[Merge → npm publish triggered]
Reviews (5): Last reviewed commit: "chore(release): version apps" | Re-trigger Greptile |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
c3216f5 to
6a73f0b
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
6a73f0b to
c9746a5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
c9746a5 to
8344e7d
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
8344e7d to
f5fd650
Compare
Releases: ensapi@1.12.0 @ensnode/ensnode-sdk@1.12.0 ensindexer@1.12.0 ensadmin@1.12.0 ensrainbow@1.12.0 fallback-ensapi@1.12.0 @namehash/ens-referrals@1.12.0 @ensnode/ensdb-sdk@1.12.0 @ensnode/ensnode-react@1.12.0 @ensnode/ensrainbow-sdk@1.12.0 @ensnode/integration-test-env@1.12.0 @namehash/namehash-ui@1.12.0 @docs/ensnode@1.12.0 @docs/ensrainbow@1.12.0 enssdk@1.12.0 enscli@1.12.0 enskit@1.12.0 ensskills@1.12.0 @ensnode/datasources@1.12.0 @ensnode/ponder-sdk@1.12.0 @ensnode/ponder-subgraph@1.12.0 @ensnode/shared-configs@1.12.0 @ensnode/ensindexer-perf-testing@1.12.0 @ensnode/enskit-react-example@0.0.5 [skip ci]
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
f5fd650 to
843693e
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 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
@ensnode/ensnode-sdk@1.12.0
Minor Changes
4fb7b33Thanks @shrugs! - Breaking (@ensnode/ensnode-sdk):getRootRegistryIdsis removed; use the newisRootRegistryId(namespace, registryId)predicate to test root membership instead.getRootRegistryId(singular, "preferred root") is unchanged.Patch Changes
@namehash/ens-referrals@1.12.0
Patch Changes
4fb7b33]:@ensnode/ensdb-sdk@1.12.0
Patch Changes
4fb7b33]:enskit@1.12.0
Patch Changes
@ensnode/ensnode-react@1.12.0
Patch Changes
4fb7b33]:@ensnode/ensrainbow-sdk@1.12.0
Patch Changes
@namehash/namehash-ui@1.12.0
Patch Changes
4fb7b33]:@ensnode/datasources@1.12.0
enssdk@1.12.0
ensskills@1.12.0
@ensnode/ponder-sdk@1.12.0
@ensnode/ponder-subgraph@1.12.0
ensapi@1.12.0
Minor Changes
#2061
4fb7b33Thanks @shrugs! - Omnigraph: exposeDomain.canonicalandRegistry.canonicalon the Omnigraph schema. Both are non-nullBoolean!fields indicating whether the entity participates in the Canonical Nametree.#2061
4fb7b33Thanks @shrugs! - Omnigraph (breaking): drop thecanonical: Boolean = falsefield fromDomainsWhereInput(used byQuery.domains). Every nameable Domain is canonical by definition, so the filter was redundant; the query now always scopes to Canonical Domains. Consumers passingwhere: { canonical: true }should drop the field; consumers relying oncanonical: false(or default) to surface non-canonical Domains via this query no longer can — readDomain.canonicaldirectly or scope byAccount.domains/Registry.domainsinstead.#2077
c2e1047Thanks @shrugs! - Omnigraph: add anENSProtocolVersionenum (ENSv1|ENSv2) andwhere: { version }filter onQuery.domainsandAccount.domains.#2061
4fb7b33Thanks @shrugs! - Omnigraph (breaking):Resolver.bridgedis no longer anAccountIdscalar; it now returns the bridged targetRegistryinterface. Consumers should change their selection frombridged(scalar) tobridged { ... }(Registry interface) — the new shape exposes the fullRegistryand allows navigation into the bridged sub-registry's canonical Domain etc.Patch Changes
4fb7b33]:ensadmin@1.12.0
Patch Changes
4fb7b33]:ensindexer@1.12.0
Patch Changes
#2073
9785be0Thanks @shrugs! - ENSIndexer ensv2 plugin: correctly handle non-UTF-8string labelargs inRegistrarController:NameRegisteredand:NameRenewedevents. ABI-decoding replaces non-UTF-8 byte sequences with U+FFFD, which then fails the labelhash round-trip. Previously this threw a fatalInvariant(RegistrarController:NameRegistered)and aborted the run; now the label is treated as unemitted and the heal path indexes the registration under the canonicallabelHash.Updated dependencies [
4fb7b33]:ensrainbow@1.12.0
Patch Changes
4fb7b33]:fallback-ensapi@1.12.0
Patch Changes
4fb7b33]:@docs/ensnode@1.12.0
Patch Changes
@docs/ensrainbow@1.12.0
Patch Changes
@ensnode/enskit-react-example@0.0.5
Patch Changes
@ensnode/integration-test-env@1.12.0
Patch Changes
4fb7b33]:enscli@1.12.0
@ensnode/ensindexer-perf-testing@1.12.0
@ensnode/shared-configs@1.12.0