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

Chore: Fix SDK fork's branches and ensure osmosis-main and v16.x match #5255

Closed
Tracked by #4700
nicolaslara opened this issue May 22, 2023 · 2 comments
Closed
Tracked by #4700

Chore: Fix SDK fork's branches and ensure osmosis-main and v16.x match #5255

nicolaslara opened this issue May 22, 2023 · 2 comments
Assignees
@mattverse

Comments

@nicolaslara
Copy link
Contributor

No description provided.

@nicolaslara nicolaslara mentioned this issue May 22, 2023
Closed
@github-project-automation github-project-automation bot moved this to Needs Triage 🔍 in Osmosis Chain Development May 22, 2023
@p0mvn
Copy link
Member

p0mvn commented May 23, 2023

@mattverse assigning you based on earlier discussions in chain dev

TODOs:

  • check v16 includes everything that is on osmosis-main
  • delete osmosis-main
  • make osmosis-main off of v16.x (ping Dev if no permissions)

@p0mvn p0mvn moved this from Needs Triage 🔍 to Todo 🕒 in Osmosis Chain Development May 23, 2023
@stackman27
Copy link
Contributor

stackman27 commented Jun 3, 2023 •
edited
Loading

i believe we can close this right as it's handled here #5409

@github-project-automation github-project-automation bot moved this from Todo 🕒 to Done ✅ in Osmosis Chain Development Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattverse mattverse

Labels
None yet
Projects
Osmosis Chain Development
Archived in project
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nicolaslara @ValarDragon @stackman27 @p0mvn @mattverse