Release New Version#2282
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 a standard Changesets-generated release PR bumping all packages from
Confidence Score: 5/5Fully automated Changesets release PR — safe to merge once the team is ready to cut the 1.16.0 release. All changes are mechanical: version strings in package.json files, changelog entries, Docker default image tags, and the OpenAPI info.version field. No production logic is modified in this PR itself; the substantive code changes were already reviewed and merged via the individual feature PRs referenced in the changelogs. No files require special attention — every change is a version-string update generated by the Changesets toolchain. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
CS[Changesets consumed\n.changeset/*.md deleted] --> VB[Version bump\n1.15.2 → 1.16.0]
VB --> PKG[package.json updates\n~28 packages]
VB --> CL[CHANGELOG.md updates\n~28 changelogs]
VB --> DC[Docker service files\ndefault image tags updated]
VB --> OA[ensapi-openapi.json\ninfo.version updated]
PKG --> PUB[Ready to publish\nto npm]
DC --> DPL[Docker images\nreferenced by operators]
Reviews (8): Last reviewed commit: "chore(release): version apps" | Re-trigger Greptile |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
aafbd6b to
9601c7a
Compare
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Additional Suggestions:
- Missing pnpm install in release:postversion script causes stale lockfile after changeset version, leading to ERR_PNPM_OUTDATED_LOCKFILE in all builds
- upsertResolver function does not return the resolver record, but multiple callers depend on the return value to access resolver properties
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
9601c7a to
61ab4ab
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
61ab4ab to
dabc4fb
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
dabc4fb to
5758984
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
5758984 to
6616c5f
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
6616c5f to
0638b39
Compare
Releases: ensapi@1.16.0 ensskills@1.16.0 ensindexer@1.16.0 ensadmin@1.16.0 ensrainbow@1.16.0 fallback-ensapi@1.16.0 enssdk@1.16.0 enscli@1.16.0 enskit@1.16.0 @ensnode/datasources@1.16.0 @ensnode/ensrainbow-sdk@1.16.0 @ensnode/ensdb-sdk@1.16.0 @ensnode/ensnode-sdk@1.16.0 @ensnode/integration-test-env@1.16.0 @ensnode/ponder-sdk@1.16.0 @ensnode/ponder-subgraph@1.16.0 @ensnode/shared-configs@1.16.0 @docs/ensnode@1.16.0 @docs/ensrainbow@1.16.0 @namehash/ens-referrals@1.16.0 @namehash/namehash-ui@1.16.0 @ensnode/ensindexer-perf-testing@1.16.0 @ensnode/enskit-react-example@0.0.11 @ensnode/enssdk-example@0.0.5 [skip ci]
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
0638b39 to
9889b40
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
ensskills@1.16.0
Minor Changes
7f7627aThanks @shrugs! - Theenssdkandenskitskills are now fully authored (previously stubs):enssdkcovers the typed ENS Omnigraph client (gql.tada), hashing, normalization, and interpretation primitives for TypeScript integrations;enskitcovers building ENS React UIs (provider setup, typed Omnigraph hooks, caching, Relay pagination). Theens-protocolskill also gained the Subgraph-Interpreted Label concept (why subgraph-compatible APIs may return an Encoded LabelHash where the Omnigraph returns the literal label).Patch Changes
7f7627aThanks @shrugs! - Theomnigraphskill now explains Protocol Acceleration (resolve is accelerated by default, transparent protocol-compliant fallback, theacceleration { requested attempted }introspection) and the indexing-status/503 contract (when an instance responds 503 and how to check progress withenscli ensnode indexing-status). Theens-protocolskill now defines the ENS Namespace concept (a logically-isolated set of names spanning many chains, not 1:1 with an L1 chain).@ensnode/datasources@1.16.0
Patch Changes
@namehash/ens-referrals@1.16.0
Patch Changes
enscli@1.16.0
Patch Changes
@ensnode/ensdb-sdk@1.16.0
Patch Changes
enskit@1.16.0
Patch Changes
@ensnode/ensnode-sdk@1.16.0
Patch Changes
@ensnode/ensrainbow-sdk@1.16.0
Patch Changes
@namehash/namehash-ui@1.16.0
Patch Changes
enssdk@1.16.0
@ensnode/ponder-sdk@1.16.0
@ensnode/ponder-subgraph@1.16.0
ensadmin@1.16.0
Patch Changes
ensapi@1.16.0
Patch Changes
#2285
ba68bbeThanks @sevenzing! - - AddDomain.resolve.profile.contenthashinterpretationUpdated dependencies []:
ensindexer@1.16.0
Patch Changes
#2280
dff338cThanks @shrugs! - ENSIndexer now re-derives a Resolver's ENSIP-10IExtendedResolversupport when a known proxy Resolver emits an EIP-1967Upgradedevent, instead of fixing the value once at first visibility. Proxy Resolvers that activateIExtendedResolvervia a post-assignment upgrade (e.g. the 3DNS Resolver behind.box) were stuckextended = falseforever, silently breaking wildcard resolution for affected names.Updated dependencies []:
ensrainbow@1.16.0
Patch Changes
fallback-ensapi@1.16.0
Patch Changes
@docs/ensnode@1.16.0
Patch Changes
@docs/ensrainbow@1.16.0
Patch Changes
@ensnode/enskit-react-example@0.0.11
Patch Changes
@ensnode/enssdk-example@0.0.5
Patch Changes
@ensnode/integration-test-env@1.16.0
Patch Changes
@ensnode/ensindexer-perf-testing@1.16.0
@ensnode/shared-configs@1.16.0