Remove contract registry - moved to dedicated repository #77
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The contract registry functionality has been moved to a dedicated repository at https://github.com/burnt-labs/deployed-contract-listings This change: - Removes contracts.json and related scripts - Removes package.json dependencies used only for the registry - Updates README with notice about the new location - Keeps only the contract source code in this repository The new dedicated repository provides: - Interactive web interface with search and filtering - Modern Xion Dashboard design system - GitHub Pages deployment - Better separation of concerns between contract code and registry
Removes workflows that were specific to the contract registry: - validate.yml: Used to validate contracts.json and README sync - verify-contracts.yml: Used to verify deployed contracts daily Keeps the essential workflows for contract development: - Basic.yml: Rust test suite for contract compilation - Release.yml: WASM release workflow for contract artifacts
The old PR template was entirely focused on adding contracts to the registry. This new template is appropriate for actual contract development PRs. New template includes: - Type of change (bug fix, feature, breaking change, etc.) - Which contracts are affected (Account, Treasury, User Map) - Testing checklist - General development checklist This aligns with the repository's new focus on contract source code rather than the deployed contract registry.
The PR template was specific to the contract registry. Since the repository now focuses on contract source code, a PR template is not necessary. Developers can provide relevant context as needed for each PR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
contracts.json- now in dedicated repopackage.jsonandpackage-lock.json- only used for registry scriptsscripts/directory with registry utilitiesWhy This Change?
The contract registry is better suited as a standalone project because:
New Repository Features
The dedicated registry repository provides:
Test Plan