chore(repo): version packages for stable - #1052
Merged
Merged
Conversation
knock-eng-bot
requested review from
BenaventeX24 and
kylemcd
and removed request for
a team
July 28, 2026 13:14
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Bundle ReportBundle size has no change ✅ |
knock-eng-bot
force-pushed
the
changeset-release/main
branch
from
July 28, 2026 15:27
34a4235 to
d12e7f1
Compare
knock-eng-bot
force-pushed
the
changeset-release/main
branch
from
July 29, 2026 19:20
d12e7f1 to
4fd0c34
Compare
knock-eng-bot
force-pushed
the
changeset-release/main
branch
from
July 29, 2026 22:03
4fd0c34 to
6e5172c
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1052 +/- ##
=======================================
Coverage 73.00% 73.00%
=======================================
Files 139 139
Lines 4342 4342
Branches 1275 1275
=======================================
Hits 3170 3170
Misses 1055 1055
Partials 117 117 |
kylemcd
approved these changes
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@knocklabs/expo@0.8.0
Minor Changes
e52c4ef: chore(deps): bump react-native-get-random-values from 1.11.0 to 2.0.0
v2 of the polyfill is new architecture only and requires React Native >= 0.81
(Expo SDK >= 54).
@knocklabs/react-nativeimports it for its side effects fromsrc/index.ts, so that floor now applies to every consumer of the package, andto
@knocklabs/expoby way of its dependency on@knocklabs/react-native.The
react-nativepeer range on both packages has been narrowed from*to>=0.81, so installs on unsupported versions surface a peer warning instead offailing at runtime when the native module is missing. Expo SDK 54 is the release
that ships React Native 0.81, so the
expopeer stays at*and thereact-nativeconstraint covers both.Patch Changes
@knocklabs/react@0.13.0
Minor Changes
7e3ee26: Drop React 16 support
@knocklabs/reactand@knocklabs/react-corenow compile with React'sautomatic JSX runtime, so their published output imports
react/jsx-runtime.That entry point only exists in React 17 and later, so the
reactandreact-dompeer ranges narrow from^16.11.0 || ^17.0.0 || ^18.0.0 || ^19.0.0to
^17.0.0 || ^18.0.0 || ^19.0.0.If you are on React 16, stay on the previous release. Everyone on React 17+ can
upgrade with no code changes.
This comes out of the move to Vite 8, which compiles JSX with oxc before Babel
runs, making the previous classic-runtime setup (
jsxRuntime: "classic"plusbabel-plugin-react-require) unworkable.Patch Changes
@knocklabs/react-core@0.15.0
Minor Changes
7e3ee26: Drop React 16 support
@knocklabs/reactand@knocklabs/react-corenow compile with React'sautomatic JSX runtime, so their published output imports
react/jsx-runtime.That entry point only exists in React 17 and later, so the
reactandreact-dompeer ranges narrow from^16.11.0 || ^17.0.0 || ^18.0.0 || ^19.0.0to
^17.0.0 || ^18.0.0 || ^19.0.0.If you are on React 16, stay on the previous release. Everyone on React 17+ can
upgrade with no code changes.
This comes out of the move to Vite 8, which compiles JSX with oxc before Babel
runs, making the previous classic-runtime setup (
jsxRuntime: "classic"plusbabel-plugin-react-require) unworkable.@knocklabs/react-native@0.11.0
Minor Changes
e52c4ef: chore(deps): bump react-native-get-random-values from 1.11.0 to 2.0.0
v2 of the polyfill is new architecture only and requires React Native >= 0.81
(Expo SDK >= 54).
@knocklabs/react-nativeimports it for its side effects fromsrc/index.ts, so that floor now applies to every consumer of the package, andto
@knocklabs/expoby way of its dependency on@knocklabs/react-native.The
react-nativepeer range on both packages has been narrowed from*to>=0.81, so installs on unsupported versions surface a peer warning instead offailing at runtime when the native module is missing. Expo SDK 54 is the release
that ships React Native 0.81, so the
expopeer stays at*and thereact-nativeconstraint covers both.Patch Changes
@knocklabs/eslint-config@0.0.7
Patch Changes
@knocklabs/expo-example@1.1.11
Patch Changes
guide-example@0.0.87
Patch Changes
ms-teams-connect-example@0.0.74
Patch Changes
nextjs-app-dir-example@0.0.73
Patch Changes
nextjs-example@1.2.39
Patch Changes
slack-connect-example@0.3.73
Patch Changes
slack-kit-example@0.4.71
Patch Changes