Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Updated near-deps to 0.23.0 #148

Merged
merged 2 commits into from
Jun 18, 2024
Merged

chore: Updated near-deps to 0.23.0 #148

merged 2 commits into from
Jun 18, 2024

Conversation

akorchyn
Copy link
Collaborator

@akorchyn akorchyn commented Jun 18, 2024

Technically it is a breaking change since we now depend on the newer version of near-* crates and thus the upstream dependencies should also update them.

It is not a breaking change since developers can still use the older near-* versions

@akorchyn akorchyn marked this pull request as ready for review June 18, 2024 15:08
@frol frol changed the title [chore] Updated near-deps to 0.23.0 chore!: Updated near-deps to 0.23.0 Jun 18, 2024
Copy link
Collaborator

@frol frol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@akorchyn How do you feel about this direction? This way we would still need to update near-jsonrpc-client to bump the upper range, but we won't cause upstream dependencies needing to update all or nothing to avoid duplicated crates

Cargo.toml Outdated Show resolved Hide resolved
@akorchyn
Copy link
Collaborator Author

I don't mind. Let's try 👍🏻

@frol frol changed the title chore!: Updated near-deps to 0.23.0 chore: Updated near-deps to 0.23.0 Jun 18, 2024
@frol frol enabled auto-merge (squash) June 18, 2024 15:58
@frol frol merged commit b0fff1c into near:master Jun 18, 2024
4 checks passed
@frol frol mentioned this pull request Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants