ci: pr and release

[hoangndst]

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

• N
• Y

fix #4

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• N
• Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• Unit test
• Integration test
• Benchmark (add benchmark stats below)
• Manual test (add detailed scripts or steps below)
• Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[hoangndst]

This pull request introduces a release management system using Changesets, adds CI/CD workflows for automated testing and publishing, and assigns code ownership for specific files. The most important changes include setting up Changesets configuration, implementing CI and release workflows, and adding scripts for release checks and tag creation.

Release Management System:

• Added a Changesets folder with a README explaining its purpose and a config.json file to configure versioning and publishing settings. (.changeset/README.md, .changeset/config.json) [1] [2]

CI/CD Workflows:

• Added a ci.yml workflow to automate linting, testing, building, and dependency installation for pull requests and pushes to the main branch. (.github/workflows/ci.yml)
• Added a release.yml workflow to handle version updates and publishing of packages, including a conditional release step based on version changes. (.github/workflows/release.yml)

Release Automation Scripts:

• Created a check-if-release.js script to determine if a release is needed by checking for package version bumps between commits. (scripts/ci/check-if-release.js)
• Added a create-tag.js script to generate Git tags for package releases based on their versions. (scripts/ci/create-tag.js)