Semantic versioning for v7

[faddat]

Works on: #788

Description

Semantic versioning for osmosis v7

---

For contributor use:

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer

[mattverse]

Should be good to merge once go.mod sdk version is reverted to original state!

[ValarDragon]

I am generally lost as to what is standard for golang projects. Is it to make main with breaking changes with one version higher, or is it with the same last major release.

Also how do golang projects do backports with these version import differences :/

[mattverse]

From my knowledge its make breaking changes with one version higher.

[mattverse]

Also how do golang projects do backports with these version import differences :/
@ValarDragon wdym? Can you give an example ?

[faddat]

You know, there's an issue in this, too. I'm going to jump off of main a second time, to avoid it.

[faddat]

@ValarDragon if you still want to use mergify, we need to add it to this repo. I am going to close this one because I think it might add commits of Sunny's not meant for main.

Also seems like some of the wasm tests are trying to import /x/ibc

I think I got halfway through an upgrade of the tests w/ Juno and it should be the same kind of thing so I'll try and fix them.

It turned out to be quite easy to resolve and was not related to the wasm code 🍾

[codecov-commenter]

Codecov Report

Merging #804 (d495ac5) into main (e7ab669) will decrease coverage by 0.09%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #804      +/-   ##
==========================================
- Coverage   20.30%   20.21%   -0.10%     
==========================================
  Files         191      192       +1     
  Lines       24740    24854     +114     
==========================================
  Hits         5023     5023              
- Misses      18793    18907     +114     
  Partials      924      924              

Impacted Files	Coverage Δ
app/upgrades/v4/upgrades.go	100.00% <ø> (ø)
store/legacy/v101/tree.go	77.77% <ø> (ø)
store/tree.pb.go	38.40% <ø> (ø)
v043_temp/address/hash.go	80.00% <ø> (ø)
x/claim/abci.go	0.00% <ø> (ø)
x/claim/client/cli/query.go	34.45% <ø> (ø)
x/claim/client/cli/tx.go	0.00% <ø> (ø)
x/claim/genesis.go	60.00% <ø> (ø)
x/claim/handler.go	0.00% <ø> (ø)
x/claim/keeper/claim.go	64.33% <ø> (ø)
... and 123 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e7ab669...d495ac5. Read the comment docs.

[faddat]

@mattverse this is complete and I've merged the latest main branch now, too.

[mattverse]

LGTM! Thanks for this @faddat

In the future, we don't want main to have sem-ver of the next major release, but sem-ver for the latest release, since that would make sense for all the backporting that would be happening. Since we have a major upgrade coming up soon, this PR, in particular, makes sense + super helpful!

[ValarDragon]

Lets re-delete this file

[ValarDragon]

Thanks for the in-depth review @mattverse / checking what other projects do as the standard here.

Did a quick skim, and only saw the v7 change + the re-added legacy.go file.

Lets also file an issue to add the semver situation to the contributing.md

[ValarDragon]

Going to go ahead and merge before this is broken by the next PR