Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update the repo with the latest changes #66

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

huaweigu
Copy link
Contributor

@huaweigu huaweigu commented Jan 29, 2025

Summary

I've synced the code from the development repository to this repository. I also manually validated the hash using the following command:

(
  jq -c '.dependencies' package.json | sha256sum
  find src test .gitmodules -type f -exec sha256sum {} \;
) | sha256sum

Result:
b991dd44c4d15e0d9299403773efc60f441e8d04d67924af972dead0f5fa409d (both repos)

This ensures the integrity of the sync.

Detail

Changeset

  • Sync src/
  • Sync dependencies in package.json

Checklist

  • Did you add new tests and confirm all tests pass? (yarn test)
  • Did you update relevant docs? (docs are found in the docs folder)
  • Do your commits follow the Conventional Commits standard?
  • Does your PR title also follow the Conventional Commits standard?
  • If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
  • Did you run lint (yarn lint) and fix any issues?
  • Did you run formatter (yarn format:check) and fix any issues (yarn format:write)?

Testing

  • Sync test/

Documentation

n/a

@huaweigu huaweigu marked this pull request as ready for review January 29, 2025 16:35
@huaweigu huaweigu changed the title chore: sync the recent development chore: update the repo with latest change Jan 29, 2025
@huaweigu huaweigu changed the title chore: update the repo with latest change chore: update the repo with the latest changes Jan 29, 2025
@weikangsong weikangsong merged commit 50a1708 into circlefin:master Jan 29, 2025
6 checks passed
huaweigu pushed a commit that referenced this pull request Jan 31, 2025
🤖 I have created a release *beep* *boop*
---


##
[2.1.2](v2.1.1...v2.1.2)
(2025-01-29)


### Miscellaneous Chores

* update the repo with the latest changes
([#66](#66))
([50a1708](50a1708))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
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.

3 participants