fix(processor): make sure typebox has the 0.33.x
semvar so that it remains compatible with fastify typebox plugin
#266
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.
The #261 is failing cause of the following issue. Is the same for all connectors. I will update those if we approve of this PR.
In dependabot the
@sinclair/typebox
is trying to get bumped to0.34.3
however the@fastify/type-provider-typebox
package has a peerDependency for@sinclair/typebox
specified as>=0.26 <=0.33
.So as long as the fastify typebox plugin does not get updated we won't be able to install a new version of
@sinclair/typebox
. This PR updates thepackage.json
so that we will only allow0.33.x
versions thus satisfying the peerDependency. The dependabot PR should work again after rebasing once this merged.This is the error message from
npm
:This change will at the long term introduce a tiny bit of maintenance since we will never go above
0.33.x
. So if fastity typebox plugin gets updated to support newer versions of typebox we would need to manually update the semver range as done in this pr. But this approach is better then to force it using a resolution.