-
Notifications
You must be signed in to change notification settings - Fork 307
refactor(sdk): remove Jinja prompts superseded by the Python prompt registry #3796
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟠 Important: This changes the documented custom security policy from a Jinja template into raw file contents. The public field still says
Security policy template filename, and the old path rendered custom policies through Jinja with the normal template context, so existing policies using{{ ... }},{% include %}, or filters will now be injected literally. Either keep custom policies rendered throughrender_template(...)before passing the content into the registry, or make this an explicit breaking contract change with docs/deprecation and tests that prove the new raw-text behavior is intentional.