Skip to content

Commit

Permalink
build(blade): update version (#2528)
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
rzpcibot and github-actions[bot] authored Feb 5, 2025
1 parent e50729d commit 37c12f3
Show file tree
Hide file tree
Showing 3 changed files with 18 additions and 17 deletions.
16 changes: 0 additions & 16 deletions .changeset/afraid-chefs-beam.md

This file was deleted.

17 changes: 17 additions & 0 deletions packages/blade/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,22 @@
# @razorpay/blade

## 11.40.3

### Patch Changes

- e50729d1: fix(FileUpload): revert to not calling onChange on file remove

> [!NOTE]
>
> Check the below timeline if you're upgrading from 11.34.1+ version to this version
**Timeline of FileUpload changes**

- In 11.34.1: We did not call onChange on removing of file. Only onRemove was called
- In 11:36.2: We added dispatchEvent call which started calling onChange on onRemove (since React treats `input type="file"` differently than `input type="text"` - [CodeSandbox Link](https://codesandbox.io/p/sandbox/friendly-ishizaka-yk7mm3))
- In 12.4.0: We released a fix thinking onChange call was expected behaviour and we just updated the state value for it
- **This version:** Reverts back to 11.34.1 behaviour. If you're upgrading to this version from 11.34.1 or previous versions, the behaviour will stay same. If you're upgrading from 11.34.1+ and use FileUpload component, its recommended to test out FileUpload instances.

## 11.40.2

### Patch Changes
Expand Down
2 changes: 1 addition & 1 deletion packages/blade/package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "@razorpay/blade",
"description": "The Design System that powers Razorpay",
"version": "11.40.2",
"version": "11.40.3",
"license": "MIT",
"engines": {
"node": ">=18.12.1"
Expand Down

0 comments on commit 37c12f3

Please sign in to comment.