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

Bump version to 0.1.0-rc.6 #174

Merged
merged 1 commit into from
Aug 2, 2024
Merged

Bump version to 0.1.0-rc.6 #174

merged 1 commit into from
Aug 2, 2024

Conversation

aakoshh
Copy link
Contributor

@aakoshh aakoshh commented Aug 2, 2024

What ❔

Bumps the version to 0.1.0-rc.6

Why ❔

So that we can release #170 and #169 to make zksync-era backwards compatible.

@aakoshh aakoshh requested a review from brunoffranca August 2, 2024 14:15
@pompon0 pompon0 self-requested a review August 2, 2024 14:19
@aakoshh aakoshh merged commit 179b251 into main Aug 2, 2024
5 checks passed
@aakoshh aakoshh deleted the release-0.1.0-rc.6 branch August 2, 2024 14:28
github-merge-queue bot pushed a commit to matter-labs/zksync-era that referenced this pull request Aug 6, 2024
…6) (#2583)

## What ❔

Reverts #2574 to
re-establish the attestation status API integration, but also bumps the
era-consensus version to
[0.1.0-rc.6](matter-labs/era-consensus#174)
which has changes to make it backwards compatible:
* the `Executor` is started without waiting for the initial attestation
batch number to become available, so as not to stop the node completely
from participating in gossip without the main node API (this behaviour
is internal to the `AttesterStatusRunner`)
* invalid batch vote signatures are not rejected, just ignored, so the
node doesn't break connection with a peer who signed a different payload
while the feature is in flux

TODO: 
- [x] Update once `0.1.0-rc.6` is published to crates.io

## Why ❔

The first reason is to not be so eager to drop a gossip peer for
incompatibilities between newer and existing versions of the software
while we're actively working on the features involved.

The second is that the rollout strategy to mainnet seems to be to roll
out external nodes first, main nodes second. It is expected that the
external node should work with an older version of the main node, or at
least not fail to start; it is okay if a new feature doesn't work.

## Checklist

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

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

---------

Co-authored-by: Bruno França <[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