Repository navigation
feat(FOUR-34469): require version_name on deploy upsert updates - #9181
Conversation
Record deploy updates in package-versions VersionHistory (subject), matching the UI publish flow. Apply to deploy-screen, deploy-script, and deploy-process when the asset already exists. https://processmaker.atlassian.net/browse/FOUR-34469
PR SummaryMedium Risk Overview Update requests are rejected with 422 if package-versions is missing when an update is attempted, or if Feature tests cover validation and persistence; minor test harness tweaks fix script executor assertions and MySQL transaction issues in Reviewed by Cursor Bugbot for commit 4850290. Bugbot is set up for automated code reviews on this repo. Configure here. |
Extract persistDeployedScript to satisfy Sonar rule S1142. https://processmaker.atlassian.net/browse/FOUR-34469
Bind deploy version history to newly published asset versions and reject updates when version_name is provided but publish does not create a new version. https://processmaker.atlassian.net/browse/FOUR-34469
…ites - Align deploy Nayra executor test with ScriptExecutorResolver contract - Grant create-scripts permission in modules duplicate script test - Disable DB transactions in DataConnectorsServerTest to avoid MySQL 1412 - Skip duplicate-request console tests until the artisan command ships https://processmaker.atlassian.net/browse/FOUR-34469
… test Duplicate validates Script::rules() and requires script_category_id in the request body; align the modules execution_mode test with existing duplicate tests. https://processmaker.atlassian.net/browse/FOUR-34469
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 44e30d8. Configure here.
… update Pass version_name on the second deploy-screen POST so preview_presets tests align with FOUR-34469 upsert validation. https://processmaker.atlassian.net/browse/FOUR-34469
…deploy When a script update has a draft and unchanged code, HasVersioning may skip publishing a new row; attach VersionHistory to the current published version instead of returning 422. Add deploy script feature coverage for the case. https://processmaker.atlassian.net/browse/FOUR-34469
|





Record deploy updates in package-versions VersionHistory (subject), matching the UI publish flow. Apply to deploy-screen, deploy-script, and deploy-process when the asset already exists.
https://processmaker.atlassian.net/browse/FOUR-34469
ci:package-skeleton:FOUR-34469