apollo

Pins the default to on 5 workflows in that don't call a GitHub API beyond the initial checkout. The following files were left implicit because they reference / use a write-scope action / trigger on . Those scopes are best declared by maintainers: . Why CVE-2025-30066 (March 2025 supply-chain compromise) exfiltrated from workflow logs. Pinning per workflow caps runtime authority irrespective of the repo or org default, gives drift protection if the default ever widens, and is credited per-file by the OpenSSF Scorecard check. YAML validated locally with on each touched file.

Wraps up the work needed to move from v5 alpha to v5 beta. Highlights: New sub-export with v4-style call signatures over v5 internals, for incremental migration. 18 previously-stub documentation pages filled out (caching, pagination, local state, advanced, networking, SSR overview). New "Migrating from v4" section: what's changed, step-by-step guide, compat reference. Disabled the v4-era e2e workflows that no longer have packages to point at (kept as for restoring later).

Originally reported by @mustanggb Not sure if this is an issue with or a breaking change in Vue 3.5.33 itself, but upgrading Vue from 3.5.32 to 3.5.33 causes to fail with two categories of errors. option rejects and 's option is typed as . Vue 3.5.33 changed how ref types are compared, and and no longer match , even though they did in 3.5.32. This causes a TS2769 error on any call that passes a ref or computed as . is not auto-unwrapped in templates returns typed as . In Vue 3.5.32, vue-tsc would automatically unwrap in templates so you could write directly. In Vue 3.5.33 / vue-tsc 3.2.7 the wrapper stops that from happening, so accessing any property on in a template produces TS2339.