Skip to content

Commit

Permalink
chore: version packages (#104)
Browse files Browse the repository at this point in the history
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
  • Loading branch information
github-actions[bot] and github-actions[bot] authored Mar 7, 2023
1 parent 6ec1dc5 commit 6c9e328
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 11 deletions.
10 changes: 0 additions & 10 deletions .changeset/rude-lies-pretend.md

This file was deleted.

11 changes: 11 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,16 @@
# abitype

## 0.6.8

### Patch Changes

- [#100](https://github.com/wagmi-dev/abitype/pull/100) [`4263277`](https://github.com/wagmi-dev/abitype/commit/4263277e0630af8fcaedefa084d754f607c588a4) Thanks [@Raiden1411](https://github.com/Raiden1411)! - Bug fixes:

- Fixed `splitParameters` parsing behavior for tuples with too many closing or opening parentheses.
- Fixed modifiers parsing for `error`, `event`, `struct` signatures.
- Stopped allowing protected Solidity keywords as parameter names.
- Stopped allowing `calldata`, `memory`, and `storage` on non-array types (or `string`, `bytes`, and `tuple`).

## 0.6.7

### Patch Changes
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"name": "abitype",
"description": "Strict TypeScript types for Ethereum ABIs",
"license": "MIT",
"version": "0.6.7",
"version": "0.6.8",
"repository": {
"type": "git",
"url": "https://github.com/wagmi-dev/abitype.git"
Expand Down

1 comment on commit 6c9e328

@vercel
Copy link

@vercel vercel bot commented on 6c9e328 Mar 7, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Successfully deployed to the following URLs:

abitype – ./

abitype.vercel.app
abitype.dev
abitype-git-main-wagmi-dev.vercel.app
abitype-wagmi-dev.vercel.app

Please sign in to comment.