Skip to content

ci: run hh deploy scripts in CI#2843

Closed
maurelian wants to merge 2 commits intodevelopfrom
m/test-deploy-ci
Closed

ci: run hh deploy scripts in CI#2843
maurelian wants to merge 2 commits intodevelopfrom
m/test-deploy-ci

Conversation

@maurelian
Copy link
Contributor

Description

Adds a deploy step to each of the contracts packages:

      - run:
          name: Deploy
          command: npx hardhat deploy
          working_directory: packages/contracts

Even if the full devnet integration tests are not running in CI, this will be helpful for ensuring that the deploy scripts are working.

@changeset-bot
Copy link

changeset-bot bot commented Jun 23, 2022

⚠️ No Changeset found

Latest commit: e54713e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@maurelian maurelian closed this Jun 23, 2022
@maurelian maurelian deleted the m/test-deploy-ci branch December 6, 2022 20:58
theochap added a commit that referenced this pull request Dec 10, 2025
The RPC configuration had a confusing semantic mismatch between the CLI
flag and environment variable. The flag `--rpc.disabled` expects a
boolean to disable RPC when true, but the environment variable was named
`KONA_NODE_RPC_ENABLED` which suggests the opposite behavior.

This caused user confusion where setting `KONA_NODE_RPC_ENABLED=true`
would actually disable the RPC server instead of enabling it. Users
naturally expect an "ENABLED" variable to enable functionality when set
to true.

Changed the environment variable from `KONA_NODE_RPC_ENABLED` to
`KONA_NODE_RPC_DISABLED` to match the CLI flag semantics. Also updated
the comment from "Whether to enable" to "Whether to disable" for
consistency.

Co-authored-by: theo <80177219+theochap@users.noreply.github.com>
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.

1 participant