Release Process
Question
The process for publishing the build artifacts of the GrapesJS repository has had the following issues:
- Artifacts are expected to come directly from developers' machines. - https://github.com/GrapesJS/grapesjs/pull/6041
- The process is undocumented
We have multiple packages to release, and proper documentation is also needed. This ticket aims to standardize and document the release process of the GrapesJS OSS repositories, aligning with industry-standard workflows. This work will ensure consistency, reliability, and ease of use for all contributors.
Answers (0)
No answers yet.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #1516
ckeditor 5 [enhancement]
Hey @artf , as described in the following task I made a build of the ckeditor 5 which works with GrapesJS, however some of the functionalit...
Issue #6044
Node JS LTS Version
Across the codebase, we have built and linked dependencies against very old versions of Node.js. See: https://github.com/GrapesJS/grapesjs/...
Issue #3564
BUG: Unable to refresh the iframe
0.17.19 Are you able to reproduce the bug from the demo? YES What is the expected behavior? I had asked a question regarding iframe refresh...
Issue #2369
Where in the grapesjs code does it post an image to an upload endpoint?
My team and I built an application that uses grapesjs to build an email template. When pictures are introduced into the template they are a...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.