Feature: Prompt versioning

[Deepak-Kesavan]

Final refactoring and testing is in progress

What

Why

How

Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)

Database Migrations

Migrations for 'prompt_studio':

prompt_studio/prompt_studio/migrations/0007_remove_toolstudioprompt_assert_prompt_and_more.py - Remove field assert_prompt from toolstudioprompt - Remove field assertion_failure_prompt from toolstudioprompt - Remove field is_assert from toolstudioprompt - Add field checked_in to toolstudioprompt - Add field loaded_version to toolstudioprompt

Migrations for 'prompt_studio_core':

prompt_studio/prompt_studio_core/migrations/0014_customtool_tag_id.py - Add field tag_id to customtool

Migrations for 'tag_manager':

prompt_studio/tag_manager/migrations/0001_initial.py - Create model TagManager - Create model TagManagerHelper - Create constraint unique_tag_manager_prompt_id on model tagmanagerhelper - Create constraint unique_tool_tag on model tagmanager

Migrations for 'prompt_version_manager':

prompt_studio/prompt_version_manager/migrations/0001_initial.py - Create model PromptVersionManager - Create constraint unique_prompt_id_version on model promptversionmanager - Create constraint unique_prompt_fields on model promptversionmanager

Env Config

Relevant Docs

Related Issues or PRs

Dependencies Versions

Notes on Testing

Screenshots

Prompt Version Manager

Checklist

I have read and understood the Contribution Guidelines.

[sonarqubecloud[bot]]

Quality Gate failed

Failed conditions
B Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint