- commit
- 0a5caaaea7a814bc15e2f9a5d835725b2a1aa5d4
- parent
- fee4ab36ece5970f5f085fc308344dec8fa98b5a
- author
- Dami <dami.etoile@gmail.com>
| D | .editorconfig | 15 | --------------- |
| M | .gitattributes | 6 | +++++- |
| M | .gitignore | 8 | +++++--- |
| D | CHANGELOG.md | 24 | ------------------------ |
| D | CONTRIBUTING.md | 21 | --------------------- |
| D | SECURITY.md | 7 | ------- |
@@ -1,3 +1,7 @@
11 # Preserve the byte-identical upstream draw.io export runtime, including its22 # intentional indentation/trailing whitespace.3-vendor/diagramsnet/assets/js/export.js whitespace=-trailing-space3+renderers/client/diagramsnet/vendor/assets/js/export.js whitespace=-trailing-space4+5+# Wrangler owns these generated files byte-for-byte. Some runtime declarations6+# contain trailing spaces, and changing them makes `wrangler types --check` fail.7+**/worker-configuration.d.ts whitespace=-trailing-space@@ -1,24 +0,0 @@
1-# Changelog2-3-All notable DiagramZip changes are documented in this file. The project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html) and the structure from [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).4-5-## [Unreleased]6-7-### Changed8-9-- Establish DiagramZip as an independent repository, package, and hosted project.10-- Remove the inherited Maven/Vert.x gateway and its Docker, Fly.io, Antora, and smoke-test infrastructure now that the Cloudflare architecture is complete.11-12-## [0.1.0] - 2026-08-2013-14-### Added15-16-- Browser editor with Monaco, live SVG preview, diagram examples, zoom, and minimap navigation.17-- Accountless encrypted persistence backed by Cloudflare D1 and R2.18-- Documentation site and machine-readable renderer and skill catalogs.19-- Isolated JavaScript, Python, WebAssembly, and sandboxed-client renderer units for the complete catalog.20-- Shared SVG sanitization, normalization, storage, and presentation contracts.21-22-### Changed23-24-- Replaced the inherited gateway and renderer-sidecar deployment with Cloudflare-hosted shell, API, catalog, and renderer units.@@ -1,21 +0,0 @@
1-# Contributing2-3-## Before you start4-5-- Open an issue for changes that affect a public API, persistence format, renderer contract, or deployment topology.6-- Keep renderer-specific dependencies inside the relevant unit.7-- Preserve third-party attribution and update the nearest notice file when vendoring or replacing code.8-9-## Development workflow10-11-1. Create a branch from `main`.12-2. Install dependencies in the workspace or service you are changing.13-3. Make a focused change and add or update tests.14-4. Run the narrow test suite first, then the relevant build and type checks.15-5. Update `CHANGELOG.md` for user-visible changes.16-17-Commit messages should describe the behavior changed. Pull requests should explain the motivation, implementation, testing completed, and any deployment or migration requirements.18-19-## Generated files20-21-Do not edit generated documentation, Cloudflare type declarations, or build output by hand. Use the owning package's generation command and commit generated artifacts only when that package already tracks them.@@ -1,7 +0,0 @@
1-# Security policy2-3-Please do not report vulnerabilities in a public GitHub issue.4-5-Send a private report through GitHub Security Advisories for this repository. Include the affected component, reproduction steps, expected impact, and any suggested mitigation. Reports that involve a hosted endpoint should include the hostname and avoid accessing data that is not yours.6-7-The project will acknowledge a report, validate it against the current deployment, and coordinate a fix and disclosure timeline with the reporter.