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

BSR - Failure: repository has no commits #1023

Closed
byeongsu-hong opened this issue Sep 28, 2022 · 3 comments · Fixed by #1030
Closed

BSR - Failure: repository has no commits #1023

byeongsu-hong opened this issue Sep 28, 2022 · 3 comments · Fixed by #1030
Assignees
Milestone

Comments

@byeongsu-hong
Copy link

byeongsu-hong commented Sep 28, 2022

There's an error when i try to fetch wasmd's protobuf from buf.build like this

# buf.yaml
deps:
  - buf.build/cosmwasm/wasmd
$ buf mod update
Failure: repository has no commits

plus. seems like actions for publish keeps aborted due to dependency issue.
https://github.com/CosmWasm/wasmd/actions/runs/3107091489/jobs/5034779022

@alpe alpe added this to the v0.30.0 milestone Sep 28, 2022
@alpe
Copy link
Contributor

alpe commented Sep 28, 2022

Thanks for reporting! This needs to be fixed

@alpe alpe modified the milestones: v0.30.0, v0.29.0 Sep 28, 2022
@pinosu pinosu self-assigned this Sep 29, 2022
@pinosu
Copy link
Contributor

pinosu commented Sep 29, 2022

This is related to #757 .
The problem is that for push to BSR we need to define dependencies that need to be fetched from BSR, but there is not clear mappings between releases and proto files version.
@alpe I noticed that cosmos-sdk , juno and osmosis use the same approach. Should we reconsider it?

@alpe
Copy link
Contributor

alpe commented Sep 30, 2022

@pinosu I agree! This is pending for too long already. Let's use the same approach

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 a pull request may close this issue.

3 participants