Maint: Bump rive wasm to include fps counter API and take off major tag

This commit is contained in:
Zach Plata
2022-04-26 08:30:20 -07:00
committed by Zachary Plata
parent 5de40fad5b
commit 83c81b49c5
3 changed files with 9 additions and 4 deletions

View File

@@ -25,7 +25,7 @@ jobs:
run: npm config set //registry.npmjs.org/:_authToken ${{ secrets.NPM_TOKEN }}
- id: determine_version
name: Get Version
run: npm run release -- major --ci --release-version | tail -n 1 > RELEASE_VERSION
run: npm run release -- --ci --release-version | tail -n 1 > RELEASE_VERSION
working-directory: ./
env:
GITHUB_TOKEN: ${{ secrets.REPO_TOKEN }}
@@ -72,7 +72,7 @@ jobs:
- name: Release rive-react
env:
GITHUB_TOKEN: ${{ secrets.REPO_TOKEN }}
run: npm run release -- major --ci
run: npm run release -- --ci
- name: Release @rive-app/react-* variants
env:
GITHUB_TOKEN: ${{ secrets.REPO_TOKEN }}

View File

@@ -200,3 +200,8 @@ In most cases, you may be able to migrate safely. We are mainly enabling the Rea
#### Classes, styles, and component props
Starting in v2.0, we introduce one breaking change where any non-style props set on the `RiveComponent` (i.e `aria-*`, `role`, etc.) will be set on the inner `<canvas>` element. Previously, all extra props would be set onto the containing `<div>` element. Both the `className` and `style` props will continue to be set on the `<div>` element that wraps the canvas, as this dictates the sizing of the Rive component.
### Migrating to 3.0
There are no breaking changes here. If you have migrated to v2.x.x, you can safely migrate to 3.0.

View File

@@ -27,8 +27,8 @@
},
"homepage": "https://github.com/rive-app/rive-react#readme",
"dependencies": {
"@rive-app/canvas": "1.0.46",
"@rive-app/webgl": "1.0.43"
"@rive-app/canvas": "1.0.47",
"@rive-app/webgl": "1.0.44"
},
"peerDependencies": {
"react": "^16.8.0 || ^17.0.0 || ^18.0.0"