TypeChain VS semantic-release

In the two previous posts of this serie, we have learned how to build a house-swap ethereum smart-contract using solidity and how to test it using hardhat. In this post, we will create an angular application and we will install ethers to interact with the smart-contract and ethers-typechain to generate typescript types from our contract json abi.

For the wallet connection, we use WAGMI. The chat contract is connected within a React context, so that all components can interact with it. Contract interactions are also type-checked via TypeChain. These types are created on the contract development phase, but you can easily copy & paste them to your types directory at frontend, or wherever you store them.

Two parts are generally independent, except when it comes to typing. To ease contract interaction, TypeChain generates types for each contract, which can be accessed by both the Frontend and Contracts parts.

Uses typechain to auto-generate typescript bindings for compiled contracts, useful for auto-completion in your frontend dApps

Typechain GitHub Repository

AFAIK it's used quite a lot in web3, especially with React apps. Also check TypeChain ;) https://github.com/ethereum-ts/TypeChain

I can also recommend Typechain (https://github.com/ethereum-ts/TypeChain) separately or in combination with HardHat (https://hardhat.org).

Have you checked out Typechain? https://github.com/ethereum-ts/TypeChain

You can check TypeChain that creates abstraction over contracts connection based on ABI that you provide. You can find ABIs for your contract in the Hardhat build folder.

Using Conventional Commits ⭐ as a standard for your commit messages, makes Semantic Versioning 🔖 as easy as can be, with tools like Conventional Changelog 📄 Standard Version 🔖 and Semantic Release 📦🚀

Auto-tagging a project, Renovate or Dependabot can do this. With a Git Workflow and another tool like semantic-release you can do this. This behavior is a “gymnastic” to do on the CI/CD of your project but it’s not complicated. For example with GitLab CI, you can verify the pipeline run on the default branch of your project :

I'm trying to improve the security behind our release process, which uses semantic-release. During this process, it creates a change log which is committed to the repo, publishes a package and a few other things.

Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.

When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.

To further streamline deployments, I introduced semantic-release. This tool automates commit tagging and tracks changes since the previous version. As a result, deployments now occur only when new tags are present, saving us valuable minutes.