release: 1.3.1 (multiline plain-string fix)#38
Merged
Conversation
Bump version to 1.3.1 and add CHANGELOG entry for the multiline plain-string SyntaxError fix (PR #37). NOTE: This commit only carries the release metadata (version + CHANGELOG). It must sit on top of a `main` that already contains the PR #37 fix (crates/djc-template-parser/src/tag_compiler.rs). Merge PR #37 first, then apply/rebase this commit, then tag `1.3.1` to trigger the PyPI publish. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a compile test for a multiline plain-string tag value to the source-of-truth Python test file. The file previously had no such case, so the regression was only covered by the Rust test added in PR #37. This is the regression test for the PR #37 fix: it asserts that `{% component key="on click\n..." %}` compiles to a valid Python literal instead of raising `SyntaxError`. It therefore PASSES only once the PR #37 fix is present on this branch (parse + expected_tag already pass on 1.3.0; only the compile step fails pre-fix). Mirrors the same case added to django-components' tests/test_tag_parser.py. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jonathan-s
approved these changes
Jun 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(Opus 4.8)
Release djc-core 1.3.1.
What's in this PR
1.3.0→1.3.1inpyproject.toml(the version maturin publishes).Python test file (
tests/test_template_parser__tag.py::TestString::test_string_multiline_value).PR Fix multiline failure #37 fixed the bug and added a Rust test, but the Python test file had no case for it;
this closes that gap.
Why 1.3.1
PR #37 (merged) fixed a
SyntaxErrorregression from 1.3.0: a tag value that is aquoted string spanning multiple lines and containing no
{{ }}expressions (e.g. anAlpine.js / hyperscript handler) compiled to an invalid single-line Python literal.
Verification
Built a release wheel from this branch locally (
djc_core-1.3.1-cp314-…-arm64.whl) and ranthe tests against the real build:
tests/test_template_parser__tag.py::TestString— 7 passed (incl. the new test).After merge
Tag
1.3.1to trigger the PyPI publish workflow. django-components will then raise itsfloor to
djc-core>=1.3.1.🤖 Generated with Claude Code