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: bump core v1.31.0-tm-v0.34.29 #2979

Merged
merged 5 commits into from
Jan 4, 2024
Merged

Conversation

evan-forbes
Copy link
Member

@evan-forbes evan-forbes commented Jan 3, 2024

Overview

updates to the latest version of core

modifies make mod to automate calling go work sync, and then go mod tidy twice, once for the root, and then again for the testground subdir

Copy link
Contributor

coderabbitai bot commented Jan 3, 2024

Walkthrough

The update to the Makefile introduces a new command within the mod target. This command is specifically designed to update the go.mod file located in the test/testground subdirectory. This change is likely aimed at ensuring that the Go module dependencies for testground are kept up-to-date as part of the routine maintenance tasks performed by the Makefile.

Changes

File Path Change Summary
Makefile Added command to update go.mod in test/testground as part of the mod target.
Makefile Added additional echo commands for detailed output during mod target execution.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit's AI:

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your comments unless it is explicitly tagged.

  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid.
    • @coderabbitai read the files in the src/scheduler package and generate README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@evan-forbes evan-forbes added the backport:v1.x PR will be backported automatically to the v1.x branch upon merging label Jan 3, 2024
@celestia-bot celestia-bot requested a review from a team January 3, 2024 19:03
@evan-forbes evan-forbes changed the title Evan/bump core v1.30 chore: bump core v1.30.0-tm-v0.34.29 Jan 3, 2024
staheri14
staheri14 previously approved these changes Jan 3, 2024
@@ -41,6 +41,8 @@ install: go.sum
mod:
@echo "--> Updating go.mod"
@go mod tidy
@echo "--> Updating go.mod in ./test/testground"
@(cd ./test/testground && go mod tidy)
Copy link
Contributor

Choose a reason for hiding this comment

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

👍

Copy link
Collaborator

Choose a reason for hiding this comment

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

do we want a go work sync prior to both of these commands?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah makes sense

Copy link
Member Author

Choose a reason for hiding this comment

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

updated in ac5bde2

rootulp
rootulp previously approved these changes Jan 3, 2024
@@ -41,6 +41,8 @@ install: go.sum
mod:
@echo "--> Updating go.mod"
@go mod tidy
@echo "--> Updating go.mod in ./test/testground"
@(cd ./test/testground && go mod tidy)
Copy link
Collaborator

Choose a reason for hiding this comment

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

do we want a go work sync prior to both of these commands?

cmwaters
cmwaters previously approved these changes Jan 4, 2024
Copy link
Contributor

@cmwaters cmwaters left a comment

Choose a reason for hiding this comment

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

I see you weren't going to wait for my state sync fix 👀

@evan-forbes
Copy link
Member Author

evan-forbes commented Jan 4, 2024

I see you weren't going to wait for my state sync fix 👀

super sorry about that, I didn't see it until this morning and was too focused on cleaning up the leftover from the inscription stuff! fixed 🙂

@evan-forbes evan-forbes dismissed stale reviews from cmwaters, rootulp, and staheri14 via ac5bde2 January 4, 2024 16:39
@celestia-bot celestia-bot requested a review from a team January 4, 2024 16:39
@evan-forbes evan-forbes changed the title chore: bump core v1.30.0-tm-v0.34.29 chore: bump core v1.31.0-tm-v0.34.29 Jan 4, 2024
@evan-forbes evan-forbes merged commit 23d13d4 into main Jan 4, 2024
30 checks passed
@evan-forbes evan-forbes deleted the evan/bump-core-v1.30 branch January 4, 2024 18:31
mergify bot pushed a commit that referenced this pull request Jan 4, 2024
## Overview

updates to the latest version of core

modifies `make mod` to automate calling `go work sync`, and then `go mod
tidy` twice, once for the root, and then again for the testground subdir

(cherry picked from commit 23d13d4)

# Conflicts:
#	go.mod
#	go.sum
#	go.work.sum
#	test/testground/go.mod
#	test/testground/go.sum
evan-forbes added a commit that referenced this pull request Jan 4, 2024
This is an automatic backport of pull request #2979 done by
[Mergify](https://mergify.com).
Cherry-pick of 23d13d4 has failed:
```
On branch mergify/bp/v1.x/pr-2979
Your branch is up to date with 'origin/v1.x'.

You are currently cherry-picking commit 23d13d4.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   Makefile

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   go.mod
	both modified:   go.sum
	deleted by us:   go.work.sum
	deleted by us:   test/testground/go.mod
	deleted by us:   test/testground/go.sum

```


To fix up this pull request, you can check it out locally. See
documentation:
https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the
[documentation](https://docs.mergify.com/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on
`<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.com) you
can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com
</details>

---------

Co-authored-by: Evan Forbes <[email protected]>
Co-authored-by: evan-forbes <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:v1.x PR will be backported automatically to the v1.x branch upon merging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants