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

chore: follow-up of #14985 #14987

Closed
wants to merge 2 commits into from
Closed

chore: follow-up of #14985 #14987

wants to merge 2 commits into from

Conversation

julienrbrt
Copy link
Member

@julienrbrt julienrbrt commented Feb 9, 2023

Description

Follow-up of #14985 (#14985 (comment)) to decrease the id, as we can be breaking (already done in the backported PR).
Follow-up of #14979 that bumps the proto-builder.
- Note, now the proto-builder is more pedantic and verifies that protos are properly named (panic: file name testdata.proto does not start with expected testutil/testdata/; please make sure your folder structure matches the proto files fully-qualified names). This has thus to be changed in tests too.
(#14988)


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
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • 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 ! in the type prefix if API or client breaking change
  • 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)

@@ -33,6 +33,6 @@ cp -r github.com/cosmos/cosmos-sdk/* ./
cp -r cosmossdk.io/** ./
rm -rf github.com cosmossdk.io

go mod tidy
# go mod tidy # TODO to be uncommented after https://github.com/cosmos/cosmos-sdk/issues/14988
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ref #14988

@julienrbrt julienrbrt marked this pull request as ready for review February 9, 2023 22:47
@julienrbrt julienrbrt requested a review from a team as a code owner February 9, 2023 22:47
@julienrbrt julienrbrt changed the title chore: follow-ups chore: follow-up of #14985 Feb 9, 2023
@aaronc
Copy link
Member

aaronc commented Feb 10, 2023

See my comment here: #14985 (comment)

@julienrbrt julienrbrt closed this Feb 10, 2023
@julienrbrt julienrbrt deleted the julien/follow-up branch February 10, 2023 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants