Overview - @builder.io/sdks

@builder.io/sdks

7 days30 days

Latest CI Pipeline Executions

Succeeded
main
1b1b76ef chore: unmark `description` as deprecated for inputs (#4205) ## Description unmark `description` as deprecated for inputs _Screenshot_ If relevant, add a screenshot or two of the changes you made.  --- > [!NOTE] > Un-deprecates and documents `description` on `Input` types and publishes patch releases across SDK packages. > > - **Types**: > - `Input` interface: un-deprecate and document `description` in `packages/core/src/builder.class.ts` and `packages/sdks/src/types/input.ts`. > - **Releases**: > - Patch version bumps for `@builder.io/sdk`, `@builder.io/react`, and all framework SDKs listed in `.changeset/lucky-rockets-rule.md`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 417307e06de05dd60645308368c8031ef772669f. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> 
2 days ago by sidmohanty11
Succeeded
add-back-description-for-inputs
7791f24e unmark description as deprecated
3 days ago by sidmohanty11
Failed
main
955a8eac 📦 Publish SDKs (#4170) This PR was opened by the [Changesets release](https://github.com/changesets/action) 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 ## @builder.io/sdk@6.1.3 ### Patch Changes - 3e864ce: fix: incorrect conversion tracking ## @builder.io/react@8.2.9 ### Patch Changes - 3e864ce: fix: incorrect conversion tracking - Updated dependencies [3e864ce] - @builder.io/sdk@6.1.3  --- > [!NOTE] > Publish patch releases for SDK and React to fix incorrect conversion tracking, with React updating to SDK 6.1.3. > > - **Releases**: > - `@builder.io/sdk@6.1.3`: fix incorrect conversion tracking. > - `@builder.io/react@8.2.9`: fix incorrect conversion tracking; updates dependency to `@builder.io/sdk@6.1.3`. > - **Metadata**: > - Bump versions in `packages/*/package.json` and update `CHANGELOG.md` entries. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 350340b206a9d5cf8a3cbe6cc071ac618d9f5364. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>  Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 month ago by sidmohanty11
Succeeded
main
958c11b3 fix[react-gen1]: handle `fetchPriority` vs `fetchpriority` in different react versions (#4155) ## Description Handles fetch priority casing based on React versions > In a previous PR, https://github.com/vercel/next.js/pull/47302, detection for fetchPriority assumed that https://github.com/facebook/react/pull/25927 would land in react@18.3.0 because that was the react@canary version at the time. However, it didn't land in react@18.3.0 and it is expected to land in react@19.0.0 due to the breaking change. This means that users upgrading to react@18.3.0 will see a warning. Inspiration from: https://github.com/facebook/react/issues/28946 https://github.com/vercel/next.js/pull/65235 https://github.com/ascorbic/unpic-img/pull/644 _Screenshot_ If relevant, add a screenshot or two of the changes you made.
2 months ago by sidmohanty11
Succeeded
fix/handle-fetchpriority
37c39d6a Merge 611deabca68d5372877b142b58b9ec5b131222d2 into b5bb430f68a1c61f6959dc8df600a712768bda26
2 months ago by sidmohanty11
Succeeded
fix/handle-fetchpriority
4d9e7526 Merge 14989229801375d0b28deb9d7cc11c414be5ac20 into b5bb430f68a1c61f6959dc8df600a712768bda26
2 months ago by sidmohanty11
Succeeded
fix/handle-fetchpriority
003707f6 Merge 9c6854aacd449bbfd600cdba58852f532b3753c3 into b5bb430f68a1c61f6959dc8df600a712768bda26
2 months ago by sidmohanty11
Failed
main
b5bb430f 📦 Publish SDKs (#4154) This PR was opened by the [Changesets release](https://github.com/changesets/action) 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 ## @builder.io/sdk-angular@0.22.3 ### Patch Changes - f4584fa: fix: only use the edge runtime when the edge build is imported Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2 months ago by sidmohanty11
Succeeded
main
f4584fa0 fix[angular-gen2]: only use the edge runtime when the edge build is imported (#4152) ## Description As we are skipping hydration due to limitations with how we generate dynamic components we have to run eval twice - once on the server and once on the browser. The edge build was working and edge-runtime was being used but on the browser load it was fallbacking to use the browser runtime which was leading to the unsafe-eval errors. This PR fixes the issue by using edge-runtime both in the server and the browser - we will only use the edge build when users import it using: ```ts import { Content, type BuilderContent } from "@builder.io/sdk-angular/bundle/edge"; ``` Jira https://builder-io.atlassian.net/browse/ENG-10322 Screenshot <img width="2555" height="690" alt="image" src="https://github.com/user-attachments/assets/618bc9b2-e530-4547-b504-16c4be1ff369" />
2 months ago by sidmohanty11
Succeeded
fix/edge-build-unsafe-eval
b1d7d67b Merge 7d7c4baa4de09703910344004ce81d6f231d1141 into 3bb0e556c1b8c72b285cf9d746e3d3723c565884
2 months ago by sidmohanty11
Succeeded
fix/edge-build-unsafe-eval
68ad2c1d Merge 2024830d5adec34c2841c0914b01c8222e3089b3 into f645459f63da10d5830a928e1d377d2076f51d19
2 months ago by sidmohanty11
Succeeded
fix/edge-build-unsafe-eval
08d7d4fe Merge 8a3e60a361278316856a0eaf3026cb0fd2a40c4d into f645459f63da10d5830a928e1d377d2076f51d19
2 months ago by sidmohanty11
Succeeded
main
f645459f Add revalidate option to fetch request (#4147) ## Description Change related to [this ticket](https://builder-io.atlassian.net/browse/EDU-878?atlOrigin=eyJpIjoiYzAyNWUwYjMwNWNiNDNhN2ExYjc2ZWVlZGQ2YmRmZjQiLCJwIjoiaiJ9). In short, we now suggest altering caching for Next.js apps. This change should be reflected within our examples, particularly in the Integrating Pages doc.
2 months ago by sidmohanty11