Skip to content

Commit 1e320f8

Browse files
max-sixtyclaude
andauthored
chore: Prepare release 0.13.10 (#5620)
Co-authored-by: Claude <[email protected]>
1 parent af565a8 commit 1e320f8

File tree

3 files changed

+21
-26
lines changed

3 files changed

+21
-26
lines changed

.github/workflows/release.yaml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -405,6 +405,8 @@ jobs:
405405
steps:
406406
- name: 📂 Checkout code
407407
uses: actions/checkout@v5
408+
with:
409+
token: ${{ secrets.PRQL_BOT_GITHUB_TOKEN }}
408410
- run: git push origin HEAD:web --force
409411

410412
push-devcontainer:

CHANGELOG.md

Lines changed: 6 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,21 @@
11
# PRQL Changelog
22

3-
## [unreleased]
3+
## 0.13.10 — 2025-12-16
44

5-
**Language**:
5+
0.13.10 completes the npm OIDC publishing fix from 0.13.9.
66

77
**Features**:
88

9-
**Fixes**:
10-
11-
**Documentation**:
12-
13-
**Web**:
14-
15-
**Integrations**:
16-
17-
**Internal changes**:
18-
19-
**New Contributors**:
20-
21-
## [unreleased]
22-
23-
**Language**:
24-
25-
**Features**:
9+
- Add `read_json` support for DuckDB and ClickHouse (@adamnemecek, #5608)
2610

2711
**Fixes**:
2812

29-
**Documentation**:
30-
31-
**Web**:
32-
33-
**Integrations**:
13+
- Fix `text.length` on Snowflake (@priithaamer, #5614)
3414

3515
**Internal changes**:
3616

37-
**New Contributors**:
17+
- Fix npm OIDC publishing by upgrading to Node 24 (@max-sixty, #5619)
18+
- Fix push-web-branch workflow permissions (@max-sixty, #5620)
3819

3920
## 0.13.9 — 2025-12-12
4021

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

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -460,7 +460,10 @@ Currently we release in a semi-automated way:
460460
`cargo release version $version -x && cargo release replace -x && task prqlc:test-all`
461461
to bump the version, and PR the resulting commit.
462462

463-
3. After merging, go to
463+
3. Ensure all changes intended for the release are merged to `main`. Then create
464+
the release (which creates the tag on the latest commit on `main`):
465+
466+
**Web UI:** Go to
464467
[Draft a new release](https://github.com/PRQL/prql/releases/new){{footnote: Only
465468
maintainers have access to this page.}},
466469
copy the changelog entry into the release
@@ -470,6 +473,15 @@ Currently we release in a semi-automated way:
470473
or asking LLM to help.}}, enter the tag to be created, and hit
471474
"Publish".
472475

476+
**CLI:**
477+
478+
```sh
479+
gh release create $version --title "$version" --notes "$(cat <<'EOF'
480+
<paste changelog entry here>
481+
EOF
482+
)"
483+
```
484+
473485
4. From there, both the tag and release is created and all packages are
474486
published automatically based on our
475487
[release workflow](https://github.com/PRQL/prql/blob/main/.github/workflows/release.yaml).

0 commit comments

Comments
 (0)