Skip to content

Conversation

@NicoMolinaOZ
Copy link
Contributor

Documentation Pull Request

  • Fixing navigation for relayer and monitor

Summary

Type of Change

  • New documentation
  • Documentation update/revision
  • Fix typos or grammar
  • Restructure/reorganize content
  • Add examples or tutorials
  • Update API documentation
  • Other: ___________

Related Issues

Fixes #
Relates to #

Checklist

Additional Notes

@netlify
Copy link

netlify bot commented Jan 12, 2026

Deploy Preview for openzeppelin-docs-v2 ready!

Name Link
🔨 Latest commit d66dd91
🔍 Latest deploy log https://app.netlify.com/projects/openzeppelin-docs-v2/deploys/69656ec57847d50008d3a354
😎 Deploy Preview https://deploy-preview-116--openzeppelin-docs-v2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

<div className="grid grid-cols-1 lg:grid-cols-2 gap-4 sm:gap-6 mb-4 sm:mb-6">
<FeatureCard
href="/relayer"
href="/relayer/1.3.x"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want to avoid explicitly specifying the version and it should automatically show /relayer with stable latest without specifying the version. Is that not whats happening?

{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}

<APIPage document={"https://raw.githubusercontent.com/OpenZeppelin/openzeppelin-relayer/refs/heads/main/openapi.json"} operations={[{"path":"/api/v1/plugins/{plugin_id}/call","method":"post"}]} webhooks={[]} hasHead={false} />
<APIPage document={"https://raw.githubusercontent.com/OpenZeppelin/openzeppelin-relayer/refs/heads/release-v1.3.0/openapi.json"} operations={[{"path":"/api/v1/plugins/{plugin_id}/call","method":"post"}]} webhooks={[]} hasHead={false} />
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why v1.3.0 in 1.1.x?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants