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.

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

chore: Prepare boojum stage upgrade #473

Merged
merged 24 commits into from
Nov 14, 2023
Merged

chore: Prepare boojum stage upgrade #473

merged 24 commits into from
Nov 14, 2023

Conversation

StanislavBreadless
Copy link
Contributor

What ❔

Why ❔

Checklist

  • PR title corresponds to the body of PR (we generate changelog entries from PRs).
  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • Code has been formatted via zk fmt and zk lint.

@StanislavBreadless StanislavBreadless requested a review from a team as a code owner November 13, 2023 09:48
@StanislavBreadless StanislavBreadless changed the title WIP: Prepare boojum stage upgrade chore: Prepare boojum stage upgrade Nov 13, 2023
@StanislavBreadless StanislavBreadless force-pushed the sb-prepare-boojum-stage-upgrade branch from 9bfb9ee to 781248a Compare November 13, 2023 10:49
@StanislavBreadless StanislavBreadless added this pull request to the merge queue Nov 14, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 14, 2023
@perekopskiy perekopskiy added this pull request to the merge queue Nov 14, 2023
Merged via the queue into main with commit 38384e7 Nov 14, 2023
@perekopskiy perekopskiy deleted the sb-prepare-boojum-stage-upgrade branch November 14, 2023 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@perekopskiy perekopskiy perekopskiy approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@StanislavBreadless @perekopskiy