Release Process
The issues regarding the GrapesJS release process β specifically, the reliance on developer machines for artifacts and the lack of documentation β highlight a need for a standardized, automated, and transparent workflow. Adopting an industry-standard CI/CD (Continuous Integration/Continuous Delivery) pipeline will add...
Read full answer below β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 (1)
The issues regarding the GrapesJS release process β specifically, the reliance on developer machines for artifacts and the lack of documentation β highlight a need for a standardized, automated, and transparent workflow. Adopting an industry-standard CI/CD (Continuous Integration/Continuous Deliver...
Related Questions and Answers
Continue research with similar issue discussions.
Issue #3313
There are lots of click required to make text editable, can we make text field editable on a single Click.
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
Issue #3668
Cant Reset Canvas after Moving/scaling it
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
Issue #3405
An event to hook into before a block in dropped into the canvas
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
Issue #3364
@How to fix container size when we are drag element inside the container,Container will be expended according to the child dragged element. How we can auto size child element according to the parent container. Container should not be expend according to the child element. It's should be show scroll.
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins βPremium plugins ship with support, regular updates, and production-ready features β save days of integration work.
Browse premium plugins βRelated tutorials
In-depth guides on the same topic.
Tutorial
Superβ―Tooltip for GrapesJS β Versionβ―0.1.5 Released π
Weβre excited to announce the vβ―0.1.5 update of Superβ―Tooltip, our floatingβmenu and tooltip plugin for GrapesJS
Tutorial
GrapesJS in 2026: The Complete Guide to the Open-Source Web Builder Framework
Master GrapesJS in 2026. Architecture, code examples, React integration, plugin development, Studio SDK, and how it compares to other projects
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.