Update flow-go v0.37.10

[devbugging]

Update to flow-go v0.37.10

Summary by CodeRabbit

• New Features

  • Updated dependencies to improve functionality and performance, including a transition of flow-emulator to a stable release.

• Bug Fixes

  • Incremented versions of cadence and flow-go, which may include bug fixes and enhancements.

[coderabbitai]

Walkthrough

The changes involve updates to the go.mod files in the project, specifically modifying the versions of several dependencies. Key updates include incrementing the version of github.com/onflow/cadence to v1.0.0-preview.52, updating github.com/onflow/flow-go to v0.37.10, and transitioning github.com/onflow/flow-emulator from a preview version to a stable release at v1.0.0. Additionally, a new indirect dependency, github.com/onsi/ginkgo, has been introduced.

Changes

Files	Change Summary
go.mod, tests/go.mod	- Updated github.com/onflow/cadence from v1.0.0-preview.51 to v1.0.0-preview.52
	- Updated github.com/onflow/flow-go from v0.37.7-0.20240830182756-9ac9e1889c34 to v0.37.10
	- Updated github.com/onflow/flow-emulator from v1.0.0-preview.42 to v1.0.0
	- Added github.com/onsi/ginkgo at version v1.16.4

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GoModule
    participant Dependencies

    User->>GoModule: Request update
    GoModule->>Dependencies: Fetch latest versions
    Dependencies-->>GoModule: Return updated versions
    GoModule-->>User: Confirm updates applied

Loading

Poem

🐰 In the garden of code, I hop with glee,
New versions sprout, as bright as can be!
Cadence and flow, they dance in the light,
With ginkgo beside them, oh what a sight!
Bugs take their leave, improvements abound,
A joyful update, in leaps and in bounds! 🌼

---

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

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 testing code 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 and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[m-Peter]

LGTM!

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9f287a8 and d7b9d4c.

Files ignored due to path filters (2)

• go.sum is excluded by !**/*.sum
• tests/go.sum is excluded by !**/*.sum

Files selected for processing (2)

• go.mod (2 hunks)
• tests/go.mod (1 hunks)

Additional comments not posted (6)

go.mod (3)

11-11: LGTM!

The version update for github.com/onflow/cadence is approved.

---

12-12: LGTM!

The version update for github.com/onflow/flow-go is approved.

---

145-145: LGTM!

The addition of the indirect dependency github.com/onsi/ginkgo is approved.

tests/go.mod (3)

7-7: LGTM!

The update to github.com/onflow/cadence from v1.0.0-preview.51 to v1.0.0-preview.52 looks good.

---

11-11: LGTM!

The update to github.com/onflow/flow-go from v0.37.7-0.20240830182756-9ac9e1889c34 to v0.37.10 looks good.

---

9-9: Verify the impact of updating github.com/onflow/flow-emulator to v1.0.0.

Ensure that all usages of the flow-emulator package in the codebase are compatible with the stable v1.0.0 release, as this update may introduce breaking changes.

Run the following script to find all usages of the flow-emulator package: