Skip to content

Commit ea92e66

Browse files
max-sixtyclaude
andauthored
chore: Prepare 0.13.11 release changelog (#5718)
Co-authored-by: Claude <noreply@anthropic.com>
1 parent c530bc7 commit ea92e66

2 files changed

Lines changed: 27 additions & 3 deletions

File tree

CHANGELOG.md

Lines changed: 23 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,30 @@
11
# PRQL Changelog
22

3-
## [unreleased]
3+
## 0.13.11 — 2026-03-19
44

5-
**Language**:
5+
0.13.11 has 75 commits from 7 contributors. Selected changes:
66

77
**Features**:
88

9+
- Add support for `date.to_text` for BigQuery (@segv, #5712)
10+
911
**Fixes**:
1012

13+
- Prevent panic on bare `*` in `select` (@max-sixty, #5696)
14+
- Handle partial application of transforms in user-defined functions
15+
(@max-sixty, #5663; reported by @Rafferty97)
16+
- Keep Computes with Aggregate when Filter follows (@max-sixty, #5639; reported
17+
by @matiastoro)
18+
- Preserve sort before take in CTE (@max-sixty, #5638; reported by @lukapeschke)
19+
- Preserve sort with empty group `{}` (@max-sixty, #5635)
20+
- Return proper error for bare lambda expressions (@max-sixty, #5634)
21+
- Prevent DISTINCT ON internal sorting from leaking past joins (@max-sixty,
22+
#5633; reported by @annashmatko)
23+
- Fix invalid MSSQL SQL when DISTINCT and FETCH are combined (@max-sixty, #5630)
24+
1125
**Documentation**:
1226

13-
**Web**:
27+
- Editorial tweaks (@richb-hanover, #5645)
1428

1529
**Integrations**:
1630

@@ -19,8 +33,14 @@
1933

2034
**Internal changes**:
2135

36+
- Use chumsky 0.12.0 for all targets (#5659)
37+
- Update rust toolchain version (#5673)
38+
- Fix mdbook admonition syntax for mdBook 0.5 native support (#5649)
39+
2240
**New Contributors**:
2341

42+
- @segv, with #5712
43+
2444
## 0.13.10 — 2025-12-16
2545

2646
0.13.10 completes the npm OIDC publishing fix from 0.13.9.

web/book/src/project/contributing/development.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -464,6 +464,10 @@ Currently we release in a semi-automated way:
464464
echo "It has $(git rev-list --count $(git rev-list --tags --max-count=1)..) commits from $(git shortlog --summary $(git rev-list --tags --max-count=1).. | wc -l | tr -d '[:space:]') contributors. Selected changes:"
465465
```
466466

467+
When a fix closes an issue reported by someone other than the PR author,
468+
thank them in the changelog entry, e.g.
469+
`(@pr-author, #5639; reported by @issue-reporter)`.
470+
467471
2. If the current version is correct, then skip ahead. But if the version needs
468472
to be changed — for example, we had planned on a patch release, but instead
469473
require a minor release — then run

0 commit comments

Comments
 (0)