DevOps, CI/CD and Automation

Hi SQLcl experts,

We are currently adopting SQLcl 26.1 for Oracle APEX development and really like the state-based deployment approach.

Our current workflow is:

• project export
• project stage
• project release
• project gen-artifact

Feature branches are compared against the main branch using project stage, which works very well for incremental deployments.

We have one question regarding long-term maintenance.

From time to time, we would like to create a new deployment baseline, i.e. a new full installation artifact that becomes the starting point for future releases. Our intention is to avoid carrying a long history of incremental changes indefinitely.

However, according to the documentation, project stage compares the current branch against the configured base branch. Therefore, it seems that a full deployment can only be generated if the base branch itself no longer contains the previously exported objects.

Is there a recommended or intended workflow for periodically creating a new baseline in an existing SQLcl Project?

For example:

• Should the base branch be reset before creating the new baseline?
• Is there a way to use project release for this purpose?
• Or is periodic re-baselining intentionally not part of the SQLcl Project workflow?

Any guidance or best practices would be greatly appreciated.

Thank you very much!