Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
chore/bump-unreleased-docs-dates
a02a1169 chore: drop publishConfig.access from the new packages It was only needed for the first manual `npm publish`, which is done. The release publishes through changesets, and `.changeset/config.json` already sets `"access": "public"`.
by Alem Tuzlak
Succeeded
chore/bump-unreleased-docs-dates
a02a1169 Merge 66c182436a9743e243ce8cbc680d5c48675aa3f1 into d9d1e1f3dbaddf3703a8cdc7d32bd591aaa3fae6
by Alem Tuzlak
Succeeded
chore/bump-unreleased-docs-dates
1c61b013 Merge f775c5b4a8bdcf66ce314a8815b61b8c5670873e into d9d1e1f3dbaddf3703a8cdc7d32bd591aaa3fae6
by Alem Tuzlak
Succeeded
chore/bump-unreleased-docs-dates
1c61b013 chore: bump unreleased docs dates, squash changesets, bootstrap new packages Three housekeeping changes before the next release. Docs dates: every page added after the last release commit (55db7d458) is not on npm yet, so its `addedAt` is today. Their `updatedAt` is dropped — a page that ships today was never updated in public. 34 pages. Changesets: the 70 pending changesets are merged into one. The package list is the union of all of them, and each package keeps its highest bump level, so the release is identical (31 packages: 20 minor, 11 patch, 0 major). Every summary is kept in the body. New packages: `ai-byteplus`, `ai-durable-stream`, `ai-memory` and `ai-persistence` now carry `publishConfig.access: "public"`, and their versions match what is on npm after the first manual publish. npm can only attach a trusted publisher to a package that already exists, so the first version had to be published by hand; every release after this one goes through OIDC like the other packages.
by Alem Tuzlak