Skip to content

Conversation

@FabijanC
Copy link
Contributor

Changes

Checklist:

  • Validated the specification files - npm run validate_all
  • Applied formatting - npm run format
  • Performed code self-review
  • If making a new release, checked out the guidelines

@leo-starkware
Copy link
Contributor

Can you change REVERTABLE to REVERTIBLE? Other than that, LGTM

@FabijanC
Copy link
Contributor Author

Can you change REVERTABLE to REVERTIBLE? Other than that, LGTM

Addressed in e584d74

@FabijanC
Copy link
Contributor Author

Just notice that the PR currently targets master, while it should potentially be targeting a 0.9.0 release branch. I did not know which branch to choose because release/v0.9.0-rc.0 did not seem suitable -- it has already been released.

@leo-starkware leo-starkware changed the base branch from master to release/v0.9.0-rc.1 June 16, 2025 09:37
@leo-starkware leo-starkware merged commit 9377851 into starkware-libs:release/v0.9.0-rc.1 Jun 19, 2025
@FabijanC FabijanC deleted the l1-handler-tx-trace branch June 25, 2025 13:43
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.

L1_HANDLER_TXN_TRACE should include revert_reason

2 participants