Skip to content

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 zkstack dev fmt and zkstack dev lint.

StanislavBreadless and others added 19 commits January 15, 2025 14:58
## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] 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 `zkstack dev fmt` and `zkstack dev
lint`.
@StanislavBreadless StanislavBreadless changed the title Stage/stage-proofs upgrade info + better finalization scripts feat: Stage/stage-proofs upgrade info + better finalization scripts Feb 3, 2025
@StanislavBreadless StanislavBreadless changed the title feat: Stage/stage-proofs upgrade info + better finalization scripts chore: Stage/stage-proofs upgrade info + better finalization scripts Feb 3, 2025
@StanislavBreadless StanislavBreadless added this pull request to the merge queue Feb 3, 2025
Merged via the queue into main with commit 8ebb9f9 Feb 3, 2025
42 checks passed
@StanislavBreadless StanislavBreadless deleted the sb-stage-upgrade-info branch February 3, 2025 12:18
zkzoomer pushed a commit that referenced this pull request Jun 21, 2025
…3529)

## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] 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 `zkstack dev fmt` and `zkstack dev
lint`.

---------

Co-authored-by: Dima Zhornyk <[email protected]>
Co-authored-by: dimazhornyk <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants