Changelog

List of changes that are currently in progress and will be released soon.

Refinements to the GraphQL API and SDK.

Since the UsernameReservedNamespaceRule is applied by default to any Namespace created through the Lens factories, it is no longer necessary to specify it in the rules field when creating a Namespace.

mutation {  createUsernameNamespace(    request: {      symbol: "FOO"      namespace: "foo"      metadataURI: "lens://4f91ca…"      rules: {        required: [-         {-           usernameReservedRule: { reserved: ["asdfgh"] }-         }        ]      }    }  ) {    ... on CreateNamespaceResponse {      hash    }    ... on SelfFundedTransactionRequest {      ...SelfFundedTransactionRequest    }    ... on TransactionWillFail {      reason    }  }}

A minor renaming of GraphQL input types has been implemented. This change will only impact you if you use these input types as operation parameters, as demonstrated below.

If you are using the Lens SDK, simply update to the latest @canary version to accommodate this change.

- query ExploreQuery($request: MlexplorePostsRequest!) {+ query ExploreQuery($request: PostsExploreRequest!) {    value: mlPostsExplore(request: $request) {      __typename      items {        ...Post      }      pageInfo {        ...PaginatedResultInfo      }    }  }

- query PostsForYou($request: MlpostsForYouRequest!) {+ query PostsForYou($request: PostsForYouRequest!) {    value: mlPostsForYou(request: $request) {      __typename      items {        ...PostForYou      }      pageInfo {        ...PaginatedResultInfo      }    }  }

The Lens Metadata Standard package has reached a stable 2.0 release — no functional changes, just a transition to a stable version.

Update to:

npm install @lens-protocol/metadata@latest

to align with the stable 2.x version.

The dependency on the Lens Chain SDK has been updated to the latest stable version.

Make sure to update to the latest Lens SDK canary and Lens Chain SDK stable version.

npm install @lens-chain/sdk@latest @lens-protocol/client@canary

This release includes several bug fixes and improvements.

The Group.feed field has been upgraded to a fully-fledged Feed object. If you are using the Lens SDK, simply update to the latest version to access the new feed object.

If you are not using the SDK, update your GraphQL fragments as demonstrated below.

fragment Group on Group {  __typename  address- feed+ feed {+   ...Feed+ }  timestamp  owner  banningEnabled  membershipApprovalEnabled  metadata {    ...GroupMetadata  }  rules {    ...GroupRules  }  operations {    ...LoggedInGroupOperations  }}

In the usage below is not a breaking change per-se since any await expression implicitly wraps the value in a Promise. However, your linter/IDE may flag this as an error.

- const result = await sessionClient.getAuthenticatedUser();+ const result = sessionClient.getAuthenticatedUser();

The BanMemberGroupRule does not require any configuration because it is applied automatically when a Group is created.

import { evmAddress, uri } from "@lens-protocol/client";import { createGroup } from "@lens-protocol/client/actions";
const result = await createGroup(sessionClient, {  metadataUri: uri("lens://4f91c…"),-  rules: {-   required: [-    {-      banAccountRule: {-        enable: true,-      },-    },-   ],  },});

With this release, we redeployed a completely new protocol and reset all testnet state.

Update the latest @lens-protocol/client@canary and use the following diffs to update your GQL fragments.

To create a Post with paid-collect, group the relevant properties under the payToCollect property.

import { dateTime, evmAddress, uri } from "@lens-protocol/client";
const result = await post(sessionClient, {  contentUri: uri("lens://4f91ca…"),  actions: [    {      simpleCollect: {-       amount: {-         currency: evmAddress("0x1234…"),-         value: "42.42",-       },-       recipients: [-         {-           address: evmAddress("0x5678…"),-           percent: 30, // 30%-         },-         {-           address: evmAddress("0x9abc…"),-           percent: 70, // 70%-         },-       ],-       referralShare: 5, // 5%+       payToCollect: {+         amount: {+           currency: evmAddress("0x1234…"),+           value: "42.42",+         },+         recipients: [+           {+             address: evmAddress("0x5678…"),+             percent: 30, // 30%+           },+           {+             address: evmAddress("0x9abc…"),+             percent: 70, // 70%+           },+         ],+         referralShare: 5, // 5%+       },      },    },  ],});

The SimpleCollectActionConfig properties related to paid-collect are now grouped under the payToCollect property.

fragment SimpleCollectAction on SimpleCollectAction {  __typename  address- amount {-   ...Erc20Amount- }- recipients {-   ...RecipientPercent- }- referralShare+ payToCollect {+   __typename+   amount {+     ...Erc20Amount+   }+   recipients {+     ...RecipientPercent+   }+   referralShare+ }  collectLimit  followerOnGraph {    ...FollowerOn  }  endsAt  isImmutable  collectNftAddress}

This release introduces changes that allow resizing of Post, Account, and other metadata image URLs, as well as the option to retrieve the original Lens URIs for media URLs. Additionally, it includes various bug fixes and improvements.

UnknownAction got split into UnknownAccountAction and UnknownPostAction.

fragment AccountAction on AccountAction {  __typename  ... on TippingAccountAction {    ...TippingAccountAction  }  ... on UnknownAccountAction {-   ...UnknownAction+   ...UnknownAccountAction  }}
+ fragment UnknownAccountAction on UnknownAccountAction {+   __typename+   address+   config {+     ...AnyKeyValue+   }+   metadata {+     ...ActionMetadata+   }+ }fragment PostAction on PostAction {  ... on SimpleCollectAction {    ...SimpleCollectAction  }  ... on UnknownPostAction {-    ...UnknownAction+    ...UnknownPostAction  }}
+ fragment UnknownPostAction on UnknownPostAction {+   __typename+   address+   config {+     ...AnyKeyValue+   }+   metadata {+     ...ActionMetadata+   }+ }- fragment UnknownAction on UnknownAction {-   __typename-   address-   config {-     ...AnyKeyValue-   }-   metadata {-     ...ActionMetadata-   }- }

Some EventMetadata fields got renamed for consistency with other metadata objects.

fragment EventMetadata on EventMetadata {  …  location {-   ...EventMetadataLensLocation+   ...EventLocation  }  …  schedulingAdjustments {-   ...EventMetadataLensSchedulingAdjustments+   ...EventSchedulingAdjustments  }  …}
- fragment EventMetadataLensLocation on EventMetadataLensLocation {+ fragment EventLocation on EventLocation {  __typename  physical  virtual}
- fragment EventMetadataLensSchedulingAdjustments on EventMetadataLensSchedulingAdjustments {+ fragment EventSchedulingAdjustments on EventSchedulingAdjustments {  __typename  timezoneId  timezoneOffset}

Removed redundant title field from Graph, Feed, and Action metadata objects. Use name field instead.

fragment GraphMetadata on GraphMetadata {  __typename  description  id  name- title}

The Lens Chain SDK has been relocated under: @lens-chain/sdk. Since it's a peer dependency fo the @lens-protocol/client, you need to update the package in your project.

npm uninstall @lens-network/sdknpm install @lens-chain/sdk@canary

Fix to structural typing mismatch of AnyKeyValue union.

type ArrayKeyValue = {  __typename: "ArrayKeyValue";  key: string;+ array:- value:    | IntKeyValue    | IntNullableKeyValue    | AddressKeyValue    | StringKeyValue    | BooleanKeyValue    | RawKeyValue    | BigDecimalKeyValue    | DictionaryKeyValue;};

The TimelineItem.reposts was incorrectly returning array of Post, instead it should return array of Repost.

fragment TimelineItem on TimelineItem {  __typename  id  primary {    ...Post  }  comments {    ...Post  }  reposts {-   ...Post+   ...Repost  }}

Prepare Simple Collect Action GQL to support multi-recipient. Support at contract level coming soon.

const result = await executePostAction(sessionClient, {  post: postId("42"),  action: {-   simpleCollect: true,+   simpleCollect: {+     selected: true,+   },  },});

The whoActedOnPost query (fetchWhoActedOnPost SDK action) is now whoExecutedActionOnAccount (fetchWhoExecutedActionOnAccount SDK action).

Routine release with several bug fixes and improvements.

NestedPost and PostReference nodes got removed.

fragment Post on Post {  id  author {    ...Account  }  metadata {    ...PostMetadata  }  root {-   ...NestedPost+   ...ReferencedPost  }  quoteOf {-   ...NestedPost+   ...ReferencedPost  }  commentOn {-   ...NestedPost+   ...ReferencedPost  }  stats {    ...PostStats  }}

where:

fragment ReferencedPost on Post {  id  author {    ...Account  }  metadata {    ...PostMetadata  }
  # root, quoteOf, commentOn omitted to avoid circular references}

Lens API Testnet is now available for developers to start building and testing their applications.

The challenge mutation now requires explicit authentication roles to be passed in the request.

mutation {  challenge(    request: {-      app: "<app-address>"-      account: "<account-address>"-      signedBy: "<owner-address>"+      accountOwner: {+        app: "<app-address>"+        account: "<account-address>"+        owner: "<owner-address>"+      }    }  ) {    __typename    id    text  }}