chore: version packages - #143
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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
@github-tools/sdk@1.16.1
Patch Changes
#142
542c417Thanks @HugoRCD! - Widen the optionalevepeer dependency from>=0.44.0 <0.48.0to>=0.44.0, so@github-tools/sdk/eve-runtimeand the deprecated@github-tools/sdk/eve/@github-tools/sdk/connect/eveentry points install against current eve releases without a peer conflict. Verified against eve 0.53.These entry points keep their existing behavior and stay deprecated in favor of
@github-tools/eve-extension.@github-tools/eve-extension@0.7.1
Patch Changes
#142
542c417Thanks @HugoRCD! - Rebuild the extension against eve 0.53. eve 0.50 changed the dynamic-tool capability contract and requires extensions built against the earlier contract to be rebuilt, so agents on eve 0.50 or newer need this release.eveis now declared as a*peer dependency instead of>=0.44.0 <0.48.0. The consuming agent supplies the runtime copy of eve, and eve validates the extension's generated capability metadata at build time rather than an npm range, so a new eve release no longer produces a peer conflict. The exactevedevDependency is the authoring and build version.engines.nodewidens from24.xto>=24. Mount configuration and tool behavior are unchanged.Updated dependencies [
542c417]: