|
1 | 1 | # nostream-website |
2 | 2 |
|
| 3 | +## 1.3.0 |
| 4 | + |
| 5 | +### Minor Changes |
| 6 | + |
| 7 | +- [#884](https://github.com/cameri/nostream/pull/884) [`e654852`](https://github.com/cameri/nostream/commit/e65485297bf4d9a20ccf8f78a4aae638a22655e1) Thanks [@chappie-daemon](https://github.com/chappie-daemon)! - Add a social preview card generated from source. |
| 8 | + |
| 9 | + `website/site/scripts/build-social-card.mjs` renders one composition at two sizes: |
| 10 | + `public/media/social-card.png` (1200×630, the site's `og:image`) and |
| 11 | + `public/media/github-social-preview.png` (1280×640, the GitHub repository preview). |
| 12 | + `Base.astro` now emits the full preview set — `og:image:width`, `og:image:height`, |
| 13 | + `og:image:alt`, `twitter:image`, `twitter:title`, `twitter:description`, |
| 14 | + `og:site_name`, `og:locale` — and takes an `ogImage` prop that defaults to the card; |
| 15 | + `hero-poster.webp` stays the film's poster. |
| 16 | + |
| 17 | + The GitHub preview is uploaded by hand: **Settings → Social preview** in the |
| 18 | + repository, which no workflow can set. |
| 19 | + |
| 20 | +### Patch Changes |
| 21 | + |
| 22 | +- [#888](https://github.com/cameri/nostream/pull/888) [`07dc215`](https://github.com/cameri/nostream/commit/07dc2153d1d18e1641c8f0a079c542ab8187bcdc) Thanks [@chappie-daemon](https://github.com/chappie-daemon)! - A pull request's site preview now deploys even when the comment cannot be |
| 23 | + written, and the CDN cache is purged after a deploy so a fresh preview is not |
| 24 | + served the previous build. |
| 25 | + |
| 26 | + **A comment can no longer prevent a deploy.** The preview workflow's comment |
| 27 | + steps ran before the deploy, so a pull request opened from a fork — whose |
| 28 | + `GITHUB_TOKEN` is read-only whatever the `permissions:` block grants — failed at |
| 29 | + `GraphQL: Resource not accessible by integration (addComment)` and skipped the |
| 30 | + deploy entirely ([run 39134047965](https://github.com/cameri/nostream/actions/runs/39134047965)). |
| 31 | + The deploy now runs first, every comment step is `continue-on-error`, and the |
| 32 | + job grants `issues: write` (PR conversation comments are issue comments; |
| 33 | + `pull-requests: write` alone does not cover them). |
| 34 | + |
| 35 | + **The cache is purged after deploying**, scoped to `https://ema.tnsor.network/preview/<n>/` |
| 36 | + via the `prefixes` purge, so a stale window cannot be served — on 2026-10-18 |
| 37 | + `/preview/885/` returned production HTML for about three minutes after the |
| 38 | + build landed. The production workflow purges the whole zone after its router |
| 39 | + deploy. Both purges skip with a notice when `CLOUDFLARE_ZONE_ID` is not set for |
| 40 | + their environment, so an unconfigured environment deploys normally instead of |
| 41 | + failing. |
| 42 | + |
3 | 43 | ## 1.2.5 |
4 | 44 |
|
5 | 45 | ### Patch Changes |
|
0 commit comments