Skip to content

Conversation

@Deniallugo
Copy link
Contributor

Signed-off-by: Danil [email protected]

Conflicts:

contracts

What ❔

Why ❔

Is this a breaking change?

  • Yes
  • No

Operational changes

Checklist

  • PR title corresponds to the body of PR (we generate changelog entries from PRs).
  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • Code has been formatted via zkstack dev fmt and zkstack dev lint.

Signed-off-by: Danil <[email protected]>

# Conflicts:
#	contracts
@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2025

Hey there! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Examples of valid PR titles:

  • feat(eth_sender): Support new transaction type
  • fix(state_keeper): Correctly handle edge case
  • ci: Add new workflow for linting

Details:

No release type found in pull request title "Fix create2 factory place". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

Copy link
Contributor

@kelemeno kelemeno left a comment

Choose a reason for hiding this comment

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

once we merge contracts

Signed-off-by: Danil <[email protected]>
Signed-off-by: Danil <[email protected]>
Signed-off-by: Danil <[email protected]>

# Conflicts:
#	contracts

# Conflicts:
#	contracts
Signed-off-by: Danil <[email protected]>
Signed-off-by: Danil <[email protected]>
@Deniallugo Deniallugo force-pushed the deniallugo-new-upgrades-v30 branch from bb3ed1e to 3ef1d7c Compare December 4, 2025 23:58
@zkzoomer zkzoomer merged commit 493dae0 into kl/medium-interop-support Dec 5, 2025
27 of 39 checks passed
@zkzoomer zkzoomer deleted the deniallugo-new-upgrades-v30 branch December 5, 2025 12:37
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