feat: anchor v1 migration skill#35
Conversation
| CI — surfpool must be installed explicitly: | ||
| ```yaml | ||
| - name: Install surfpool | ||
| run: cargo install surfpool --version <pinned-version> |
There was a problem hiding this comment.
Surfpool isn't available via cargo install.
This action is what anchor uses to install surfpool: https://github.com/txtx/anchor/blob/bc92c65b2f66e8e20110570f639d3be1292890dd/.github/actions/setup-surfpool/action.yaml
I will add to linear an action to make surfpool easier to use in CI though, this is too much work for the user.
|
@tiago18c this PR is now conflicting with |
|
@lgalabru I'm moving this to draft, once we have the anchor RC out I'll finalize the PR as I want to add some other changes that are currently being finalized |
tiago18c
force-pushed
the
anchor_migration_skill
branch
from
071cbfa to
63fb766
Compare
| 3. **`anchor build`** — confirms Rust is clean. | ||
| 4. **Update TS** — rename package imports, rerun `yarn install` / `npm install`. | ||
| 5. **Run tests** — `anchor test` (surfpool) or `anchor test -- --features some-feature`. | ||
| 6. **Just before deploying** — with the v0.32 CLI still installed, close legacy IDL accounts on every cluster (see §5). Upgrading the CLI or deploying the v1 binary first makes this impossible. |
There was a problem hiding this comment.
I'm a bit confused by this directive after point 0. Step 0 says to upgrade anchor CLI, this is saying it should still be 0.32? Should this step (closing legacy IDL) actually be step 0?
|
|
||
| # Or configure surfpool | ||
| [tooling.surfpool] | ||
| logs = false |
There was a problem hiding this comment.
I don't believe logs is valid here. There's log_level, which defaults to none. Options are "trace", "debug", "info", "warn", "error"
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
4 participants
Added a new skill for anchor migration from v0.32 to v1.