Skip to content

Latest commit

 

History

History
141 lines (89 loc) · 4.47 KB

DEVELOPMENT.md

File metadata and controls

141 lines (89 loc) · 4.47 KB

Development guide

This guide will help you set up the cli locally, run tests, and use Docker for isolated testing.

Getting started

  1. Fork & Clone the repository:

First fork the repository from github and then clone it,

git clone https://github.com/{your_username}/cli.git
cd cli

After cloning the repository, you should setup the fork properly and configure the remote repository as described here

  1. Install dependencies:
npm install

Running tests

Local testing

To run all tests locally:

  • Unit tests: npm run test:unit
  • Github action tests: npm run action:test

Adding tests

  1. Create new test files in the appropriate directory under test/:

  2. Follow the existing test patterns.

  3. Run your new tests using the commands mentioned above.

Release process

To release a major/minor/patch:

Conventional Commits:

To maintain a clear git history of commits and easily identify what each commit changed and whether it triggered a release, we use conventional commits. The feat and fix prefixes are particularly important as they are needed to trigger changesets. Using these prefixes ensures that the changes are correctly categorized and the versioning system functions as expected.

For Example:

feat: add new feature

Manual

  1. Create a new release markdown file in the .changeset directory. The filename should indicate what the change is about.

  2. Add the following content to the file in this particular format:

    ---
"@package-name-1": [type] (major/minor/patch)
"@package-name-2": [type]
---

[Provide a brief description of the changes. For example: Added a new Release GitHub Flow to the Turborepo. No new features or bugfixes were introduced.]

    For Example:

    ---
"@asyncapi/cli": minor
---

Adding new Release Github Flow to the Turborepo. No new features or bugfixes were introduced.

  3. Include the file in your pull request.

Using CLI

  1. Create a new release markdown file using changeset CLI. Below command will trigger an interactive prompt that you can use to specify release type and affected packages.

    npx -p @changesets/[email protected] changeset

  2. Include the file in your pull request.

Tip

For more detailed instructions, you can refer to the official documentation for creating a changeset: Adding a changeset

Release Flow:

  1. Add a Changeset:

    • When you make changes that need to be released, create a markdown file in the .changeset directory stating the package name and level of change (major/minor/patch).

  2. Open a Pull Request:

    • Push your changes and open a Pull Request (PR). After the PR is merged the changeset file helps communicate the type of changes (major, minor, patch).

  3. CI Processes Changeset:

    • After PR is merged, a dedicated GitHub Actions release workflow runs using changeset action,

    • This action reads the markdown files in the .changeset folder and creates a PR with the updated version of the package and removes the markdown file. For example:

      Before:

      "name": "@asyncapi/cli",
"version": "2.0.1",

      After:

      "name": "@asyncapi/cli",
"version": "3.0.1",

    • The new PR will also contain the description from the markdown files,

    • AsyncAPI bot automatically merge such release PR.

  4. Release the Package:

    • After the PR is merged, the CI/CD pipeline triggers again. The changesets/action step identifies that the PR was created by itself. It then verifies if the current version of the package is greater than the previously released version. If a difference is detected, it executes the publish command to release the updated package.

Additional commands

  • Lint the code: npm run lint
  • Build Docker image: npm run docker:build

Troubleshooting

If you encounter any issues during development or testing, please check the following:

  1. Ensure you're using the correct Node.js version (18.12.0 or higher) and npm version (8.19.0 or higher).
  2. Clear the node_modules directory and reinstall dependencies if you encounter unexpected behavior.
  3. For Docker-related issues, make sure Docker is running and you have sufficient permissions.

If problems persist, please open an issue on the GitHub repository.