Skip to content

chore: Update visualizer #238

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 18, 2022
Merged

chore: Update visualizer #238

merged 1 commit into from
Oct 18, 2022

Conversation

@jimnel
Copy link
Contributor

@jimnel jimnel commented Oct 18, 2022

Changes proposed in this pull request:

  • Updates the visualizer to 4.0.0

@jimnel jimnel marked this pull request as ready for review October 18, 2022 00:28
@jimnel jimnel requested a review from a team October 18, 2022 00:28
perjlieb
perjlieb approved these changes Oct 18, 2022
View reviewed changes
Copy link
Contributor

@perjlieb perjlieb left a comment

Choose a reason for hiding this comment

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

🤡

@tachikoma-li
Copy link
Member

tachikoma-li commented Oct 18, 2022 •
edited
Loading

I guess this could be a chore PR to avoid a minor version bumping, since there is no change to the functionality in the APIs. (see here for details)

@perjlieb
Copy link
Contributor

perjlieb commented Oct 18, 2022 •
edited
Loading

I think it's not a feat though

Edit: Li beat me to this

@jimnel jimnel changed the title feat: Update visualizer chore: Update visualizer Oct 18, 2022
@jimnel jimnel merged commit a8f256a into master Oct 18, 2022
@jimnel jimnel deleted the update-visualizer branch October 18, 2022 00:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@perjlieb perjlieb perjlieb approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@jimnel @tachikoma-li @perjlieb