chore: version packages v0.2.0 🌊

[github-actions]

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

@coinbase/onchainkit@0.2.0

Minor Changes

• 218b65e: - docs: Polished README for getFrameMessage(). By @Zizzamia docs: polish README for getFrameMessage() #38

  • fix: Refactor Farcaster typing to be explicit, and added a Farcaster message verification integration test. By @robpolak @cnasc @Zizzamia fix: Refactor Farcaster typing to be explicit #37
  • feat: Added a concept of integration tests where we can assert the actual values coming back from neynar. We decoupled these from unit tests as we should not commingle. By @robpolak fix: handle neynar responses + add additional information #35
  • feat: Refactored neynar client out of the ./src/core code-path, for better composability and testability. By @robpolak fix: handle neynar responses + add additional information #35

  BREAKING CHANGES

  We made the getFrameValidatedMessage method more type-safe and renamed it to getFrameMessage.

  Before

  import { getFrameValidatedMessage } from '@coinbase/onchainkit';
  
  ...
  
  const validatedMessage = await getFrameValidatedMessage(body);

  @returns

  type Promise<Message | undefined>

  After

  import { getFrameMessage } from '@coinbase/onchainkit';
  
  ...
  
  const { isValid, message } = await getFrameMessage(body);

  @returns

  type Promise<FrameValidationResponse>;
  
  type FrameValidationResponse =
    | { isValid: true; message: FrameData }
    | { isValid: false; message: undefined };
  
  interface FrameData {
    fid: number;
    url: string;
    messageHash: string;
    timestamp: number;
    network: number;
    buttonIndex: number;
    castId: {
      fid: number;
      hash: string;
    };
  }