Skip to content
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

[CT-876] Could we also now remove our upper bound on MarkupSafe, which we put in place earlier this year due to incompatibility with Jinja2? #5506

Closed
emmyoop opened this issue Jul 20, 2022 · 0 comments · Fixed by #5507
Assignees
Labels
dependencies Changes to the version of dbt dependencies tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality
Milestone

Comments

@emmyoop
Copy link
Member

emmyoop commented Jul 20, 2022

Remove our upper bound on MarkupSafe, which we put in place earlier this year due to incompatibility with Jinja2(#4745). Also bump minimum requirement to match Jinja2's requirements.

@emmyoop emmyoop mentioned this issue Jul 20, 2022
6 tasks
@github-actions github-actions bot changed the title Could we also now remove our upper bound on MarkupSafe, which we put in place earlier this year due to incompatibility with Jinja2? [CT-876] Could we also now remove our upper bound on MarkupSafe, which we put in place earlier this year due to incompatibility with Jinja2? Jul 20, 2022
@emmyoop emmyoop added dependencies Changes to the version of dbt dependencies tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality labels Jul 20, 2022
@emmyoop emmyoop self-assigned this Jul 20, 2022
@emmyoop emmyoop added this to the v1.3 milestone Jul 20, 2022
@emmyoop emmyoop mentioned this issue Jul 21, 2022
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Changes to the version of dbt dependencies tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant