Skip to content

Feature/issue 69 module publishing#75

Open
Marshalllife wants to merge 4 commits intocedra-labs:mainfrom
Marshalllife:feature/issue-69-module-publishing
Open

Feature/issue 69 module publishing#75
Marshalllife wants to merge 4 commits intocedra-labs:mainfrom
Marshalllife:feature/issue-69-module-publishing

Conversation

@Marshalllife
Copy link
Copy Markdown

@Marshalllife Marshalllife commented Nov 5, 2025

Cedra Builders Forge - Submission

Season 1

📋 Task Information

Task Title: Issue #69: How to Publish Modules on Cedra

Overview

Comprehensive guide for publishing Move modules on Cedra blockchain with verified code examples and CLI commands.

Resolves: cedra-labs/docs/#69

Issue Link: cedra-labs/docs/69

Telegram:: t.me/marshallLife


What's Included

7-Step Publishing Workflow - From cedra move init to on-chain verification
Dependencies Management - CedraFramework with rev = "main", Git deps, local deps, conflict resolution
Versioning Strategies - SemVer, compatible/incompatible upgrades, migration patterns
Troubleshooting - 12+ common errors with tested solutions
Best Practices - Security checklist, gas optimization, documentation standards

Content Sections

  1. Publishing Workflow - Complete 7-step guide with terminal outputs
  2. Dependencies - CedraFramework setup, branch selection (rev = "main"), dependency resolution
  3. Versioning - Compatible/incompatible changes, 3 upgrade strategies
  4. Troubleshooting - Compilation, publishing, dependency, runtime errors with solutions
  5. Best Practices - Security checklist, gas tips, documentation patterns

Key Features

  • Factually Verified - All commands tested on Cedra testnet
  • Framework Branch Guidance - Documents rev = "main" (recommended) vs rev = "mainnet" (CLI default)
  • Correct Module Names - Uses cedra_framework::, cedra_token_objects::, cedra_std:: (not Aptos)
  • Real Examples - Working hello_world.move module with 100% test coverage
  • Production Ready - Zero compilation warnings, passes all tests

Stats

  • 25+ code examples (Move, Bash, TOML)
  • 30+ command examples with expected outputs
  • 12 troubleshooting scenarios with solutions

Quality Assurance

Tested - All commands verified on Cedra testnet
Accurate - Correct framework module names (`cedra_*)
Complete - Tested guild with: project structure, Move.toml, source code, automated test.sh
Formatted - Matches cedra-labs/docs Docusaurus style
Accessible - Clear explanations for beginners, depth for advanced users

Files Changed

  • docs/guides/module-publishing.md - Main guide
  • sidebars.ts - Navigation entry

📸 Demo

Screenshot:
https://res.cloudinary.com/dg6csmpkf/image/upload/v1762347807/fz0oamwitk8y0qq8w4ur.png

Live Demo:


I have read and agree to follow all Cedra Builders Forge rules.

Comprehensive guide covering the complete module publishing lifecycle:

## Key Features
- 7-step publishing workflow (init to verification)
- Dependencies management (Git, local, resolution strategies)
- Versioning strategies (SemVer, upgrade compatibility, migration paths)
- Troubleshooting guide (12+ common errors with solutions)
- Best practices (security, gas optimization, documentation)
- 25+ code examples and 30+ command examples

## Content Overview
- Step-by-step publishing: Project setup, Move.toml config, compilation, testing, publishing, verification
- Dependencies: Cedra Framework, custom Git deps, local deps, conflict resolution
- Versioning: In-place upgrades, breaking changes, migration patterns, Git tagging
- Troubleshooting: Compilation, publishing, dependency, and runtime errors
- Best practices: Security checklist, gas optimization, comprehensive documentation

## Technical Details
- 704+ lines of comprehensive documentation
- 100% Cedra-specific (no related MOVE proj. references)
- Matches cedra-labs/docs format and style
- Includes Docusaurus callouts and syntax highlighting

Resolves: cedra-labs#69
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.

1 participant