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

ci: enable backport:v3.x label #4046

Merged
merged 2 commits into from
Nov 22, 2024
Merged

ci: enable backport:v3.x label #4046

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6e453b6
ci: enable backport:v3.x label
rootulp Nov 21, 2024
b763d07
fix: lint
rootulp Nov 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .github/mergify.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,14 @@ pull_request_rules:
backport:
branches:
- v2.x
- name: backport patches to v3.x branch
conditions:
- base=main
- label=backport:v3.x
actions:
backport:
branches:
- v3.x
- name: forward-port patches to main branch (v1.x)
conditions:
- base=v1.x
Expand Down
2 changes: 1 addition & 1 deletion docs/maintainers/release-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Follow the [creating a release candidate](#creating-a-release-candidate) section
- The version tag should not include the `-rc` suffix.
- If the release targets a testnet, suffix the release with `-arabica` or `-mocha`.
- The release notes should contain an **Upgrade Notice** section with notable changes for node operators or library consumers.
- The release notes section should contain a link to https://github.com/celestiaorg/celestia-app/blob/main/docs/release-notes/release-notes.md where we capture breaking changes
- The release notes section should contain a link to <https://github.com/celestiaorg/celestia-app/blob/main/docs/release-notes/release-notes.md> where we capture breaking changes

After creating the release:

Expand Down
6 changes: 3 additions & 3 deletions docs/release-notes/release-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,10 @@ This guide provides notes for major version releases. These notes may be helpful
#### Enabling BBR and MCTCP

Consensus node operators must enable the BBR (Bottleneck Bandwidth and Round-trip propagation time) congestion control algorithm. See [#3774](https://github.com/celestiaorg/celestia-app/pull/3774).
if using linux in docker, kubernetes, a vm or baremetal, this can be done by calling
if using linux in docker, kubernetes, a vm or baremetal, this can be done by calling

```sh
make enable-bbr
make enable-bbr
```

command on the host machine.
Expand Down Expand Up @@ -54,7 +54,7 @@ You can track the tally of signalling by validators using the following query
celestia-appd query signal tally 3
```

Once 5/6+ of the voting power have signalled, the upgrade will be ready. There is a hard coded delay between confirmation of the upgrade and execution to the new state machine.
Once 5/6+ of the voting power have signalled, the upgrade will be ready. There is a hard coded delay between confirmation of the upgrade and execution to the new state machine.

To view the upcoming upgrade height use the following query:

Expand Down
Loading