fix: price-feeder version

[rbajollari]

…on command

Description

closes: #1281

This bug is happening because the price-feeder version command is trying to open the go.mod file of the price-feeder but if you're outside of that directory it doesn't know where that go.mod file is. My proposed solution is to add an argument to the version command for the directory of the price-feeder in your environment. Let me know if you have a better way to approach this.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• added appropriate labels to the PR
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[RafilxTenfen]

Hey @rbajollari, So the idea is that the price-feeder version doesn't need any go.mod to display it's current version
instead when we are building the binary with make build, it should somewhat be able to save the current git commit / tag version in which the binary was build

An idea how to do that it to look how umeed is doing umeed version

[robert-zaremba]

Please use the pattern of setting a version during the build time:

• https://github.com/umee-network/umee/blob/main/Makefile#L62
• https://github.com/umee-network/umee/blob/main/Makefile#L72

You need to adopt it in price-feeder by adding Version variable to price-feeder/main.go and setting it through ldflags as outlined above.

[adamewozniak]

Nice! Looks good to me!

[adamewozniak]

@robert-zaremba please check this out when you can

[RafilxTenfen]

Tested ACK, just a question on umeed we have umeed version which just returns like main-1f36d964a9449cb307806bef68eb90197b845274 and the --long flag, which it prints all the build deps, build flags used and cosmos SDK version

What do you think about following that pattern?

[robert-zaremba]

utACK

[adamewozniak]

Tested ACK, just a question on umeed we have umeed version which just returns like main-1f36d964a9449cb307806bef68eb90197b845274 and the --long flag, which it prints all the build deps, build flags used and cosmos SDK version

What do you think about following that pattern?

Hmm, we could add a task to add the "--long" flag, but atm I think the contents of this PR are enough (we mostly care about commit # and cosmos version with this tool) - wdyt @RafilxTenfen / @rbajollari ?

[RafilxTenfen]

Tested ACK, just a question on umeed we have umeed version which just returns like main-1f36d964a9449cb307806bef68eb90197b845274 and the --long flag, which it prints all the build deps, build flags used and cosmos SDK version
What do you think about following that pattern?

Hmm, we could add a task to add the "--long" flag, but atm I think the contents of this PR are enough (we mostly care about commit # and cosmos version with this tool) - wdyt @RafilxTenfen / @rbajollari ?

Agree