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.

Sign up for GitHub

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

Jump to bottom

fix: patch data struct #4926

Merged
merged 1 commit into from
Apr 16, 2023
Merged

fix: patch data struct #4926

merged 1 commit into from
Apr 16, 2023

Conversation

czarcas7ic
Copy link
Member

@czarcas7ic czarcas7ic commented Apr 16, 2023 •
edited
Loading

Closes: #XXX

What is the purpose of the change

The PR #4912 added a new data struct that broke an assumption of a currently merged script.

This fixes that issue.

Documentation and Release Note

  • Does this pull request introduce a new feature or user-facing behavior changes? (yes / no)
  • Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (yes / no)
  • How is the feature or change documented? (not applicable / specification (x/<module>/spec/) / Osmosis docs repo / not documented)

@czarcas7ic czarcas7ic added V:state/compatible/no_backport State machine compatible PR, depends on prior breaks no-changelog labels Apr 16, 2023
@czarcas7ic czarcas7ic requested a review from p0mvn April 16, 2023 01:41
@czarcas7ic czarcas7ic marked this pull request as ready for review April 16, 2023 01:41
@czarcas7ic czarcas7ic changed the title patch data struct fix: patch data struct Apr 16, 2023
@p0mvn p0mvn merged commit 0294419 into main Apr 16, 2023
@p0mvn p0mvn deleted the adam/patch-data-structure branch April 16, 2023 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@p0mvn p0mvn p0mvn approved these changes

Assignees
No one assigned
Labels
V:state/compatible/no_backport State machine compatible PR, depends on prior breaks
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@czarcas7ic @p0mvn