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.

Sign up for GitHub

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

Jump to bottom

chore: bump ts-custom-error #430

Merged
merged 1 commit into from
Dec 2, 2022
Merged

chore: bump ts-custom-error #430

merged 1 commit into from
Dec 2, 2022
+9 −577

Conversation

tabaktoni
Copy link
Collaborator

Fix #372

  • Performed a self-review of the code
  • Rebased to the last commit of the target branch (or merged it into my branch)
  • Linked the issues which this PR resolves
  • Documented the changes
  • Updated the docs (www)
  • Updated the tests
  • All tests are passing

@netlify
Copy link

netlify bot commented Nov 30, 2022 •
edited
Loading

✅ Deploy Preview for starknetjs ready!

Name Link
🔨 Latest commit 1af5a3f
🔍 Latest deploy log https://app.netlify.com/sites/starknetjs/deploys/6387813b0f49fe0009d52861
😎 Deploy Preview https://deploy-preview-430--starknetjs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@ivpavici ivpavici merged commit 4296cb3 into develop Dec 2, 2022
@github-actions
Copy link

github-actions bot commented Dec 5, 2022

🎉 This PR is included in version 4.15.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@tabaktoni tabaktoni deleted the fix/ts-custom-error branch March 30, 2023 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ivpavici ivpavici ivpavici approved these changes

Assignees
No one assigned
Labels
released on @next
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Found issue from ts-custom-error on v3.2.0
2 participants
@tabaktoni @ivpavici