Skip to content

Conversation

@Dargon789
Copy link

  • Because this PR includes a bug fix, relevant tests have been included.
  • Because this PR includes a new feature, the change was previously discussed on an Issue or with someone from the team.
  • I didn't do anything of this.

schaable and others added 30 commits October 23, 2025 14:13
…date-changelog-format

chore: improve the changelog formatting
…istics

Collect and display gas statistics on JavaScript/TypeScript tests
Co-authored-by: John Kane <john@kanej.me>
…hmus-missing-in-hardhat-package-while-its-available-in-nomicfoundationedr

ISTHMUS hardfork added to Hardhat 3
michalbrabec and others added 28 commits November 13, 2025 14:55
…broken-in-app-links

Documentation links aligned with new system
…-chai-matchers

Improve README docs for `hardhat-ethers-chai-matchers`
…rrror-descriptors

Export error descriptors for the website
…ing-changeset

Add missing changeset for `hardhat-network-helpers`
…ertions-docs

docs: expand reference section
…n-imports-hardhat-ethers

Add `hardhat-ethers` to the mocha+ethers devDependencies
…hout-extra-baseFeePerGas-value

Fix/network without extra base fee per gas value
…efault-chaintype

fix: use user config provided value for defaultChainType
CI:
Run the spellcheck GitHub Actions workflow on the new v1 branch in addition to existing branches.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
CI:
Trigger the v-next CI GitHub Actions workflow on the new patch-5 branch in addition to main.

https://github.com/apps/sourcery-ai
Hey there - I've reviewed your changes - here's some feedback:
If patch-5 is only a temporary or user-specific branch, consider using a branch naming pattern (e.g., patch-*) or avoiding hardcoding it in the workflow to prevent future maintenance overhead.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Adjust v-next CI workflow triggers for the patch-5 branch.
CI:
Stop running the v-next CI workflow on direct pushes to the patch-5 branch.
Run the v-next CI workflow only for pull requests targeting the patch-5 branch.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
CI:
Adjust v-next CI pull_request trigger to match branches starting with 'tag' rather than a specific patch branch.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Create config.yml

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update .circleci/config.yml

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.