Skip to content

Conversation

@joroshiba
Copy link
Member

No description provided.

@joroshiba joroshiba requested a review from jbowen93 as a code owner June 17, 2025 16:27
Copy link
Member

@jbowen93 jbowen93 left a comment

Choose a reason for hiding this comment

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

LGTM but left some questions on which versions we specify.

git clone https://github.com/astriaorg/astria.git
cd astria
git checkout tags/sequencer-v1.0.0-rc.1
git checkout tags/sequencer-v3.0.0-rc.2
Copy link
Member

Choose a reason for hiding this comment

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

why rc.2 here when we use v3.0.0 for mainnet full node?

```bash
mkdir /home/astria_org/sequencer-1.0.0-rc.1
cp ~/astria/target/release/astria-sequencer /home/astria_org/sequencer-1.0.0-rc.1/astria-sequencer
mkdir /home/astria_org/sequencer-3.0.0-rc.2
Copy link
Member

Choose a reason for hiding this comment

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

same question on rc2 as above

git clone https://github.com/astriaorg/astria.git
cd astria
git checkout tags/sequencer-v1.0.0-rc.1
git checkout tags/sequencer-v3.0.0-rc.2
Copy link
Member

Choose a reason for hiding this comment

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

same question on rc2


```bash
helm install dusk11-full-node astria/astria-sequencer-validator --version 1.0.0-rc.1 \
helm install dusk11-full-node astria/astria-sequencer-validator --version 3.0.0-rc.1 \
Copy link
Member

Choose a reason for hiding this comment

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

why is this 3.0.0-rc.1 when above we use 3.0.0 in some places and 3.0.0-rc.2 in others?

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.

3 participants