[PR #1512] [MERGED] fix(tinytorch/announcement): restore unified ecosystem template #9178

New Issue

GiteaMirror · 2026-05-03T01:25:07-05:00

GiteaMirror commented

2026-05-03 01:25:07 -05:00

📋 Pull Request Information

Original PR: https://github.com/harvard-edge/cs249r_book/pull/1512
Author: @profvjreddi
Created: 4/24/2026
Status: ✅ Merged
Merged: 4/24/2026
Merged by: @profvjreddi

Base: dev ← Head: fix/tinytorch-announcement-restore

📝 Commits (1)

48bc468 fix(tinytorch/announcement): restore unified ecosystem template

📊 Changes

1 file changed (+28 additions, -4 deletions)

View changed files

📝 tinytorch/quarto/config/announcement.yml (+28 -4)

📄 Description

Summary

The TinyTorch announcement bar was reverted during the v0.1.10 publish merge (commit `0009f55a9` on 2026-04-22) from the unified 4-line template shipped in PR #1505 back to a single-line release notice:

```
🎉 v0.1.10 released — v0.1.10 (retry after TINYTORCH_SITE path fix) · See release →
```

Restores to the template used by all eight other Quarto sites (and the StaffML React banner).

What the bar now says

```
🔥 TinyTorch — build your own ML framework from scratch; the companion framework to the textbook. [Start building →]
📘 The book: [Vol I: Foundations] · [Vol II: At Scale] — open access, free forever.
🛠️ Alongside the book: Hardware Kits (deploy) · MLSys·im (simulate) · Labs (explore)
📬 Newsletter: ML Systems insights & updates — [Subscribe →]
```

Also:

`type: info` → `type: primary` (matches the eight sibling bars' color)
adds `icon: megaphone` + `position: below-navbar` to match the shared schema
file header now documents the reversion so a future release publish doesn't silently overwrite again

Why not keep a release notice

Single-line + `type: info` breaks visual consistency with the other eight Quarto bars
"retry after TINYTORCH_SITE path fix" is commit-message-ese, not user-facing copy
Release news persists long after the release — "v0.1.10" is already stale-sounding and will look abandoned when v0.1.11 ships

If a release ever genuinely needs a top-of-bar mention, the clean way is an optional `release_note` field on the shared schema that auto-expires — not overwriting the ecosystem-navigation copy.

Test plan

YAML parses cleanly (4 content lines, `type: primary`, `dismissable: true`, `position: below-navbar`)
All pre-commit hooks passed
Post-merge: preview deploy on tinytorch site and visually confirm bar matches vol1/vol2/kits/etc.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/harvard-edge/cs249r_book/pull/1512 **Author:** [@profvjreddi](https://github.com/profvjreddi) **Created:** 4/24/2026 **Status:** ✅ Merged **Merged:** 4/24/2026 **Merged by:** [@profvjreddi](https://github.com/profvjreddi) **Base:** `dev` ← **Head:** `fix/tinytorch-announcement-restore` --- ### 📝 Commits (1) - [`48bc468`](https://github.com/harvard-edge/cs249r_book/commit/48bc46888bd61a7d497e0ed11e9024704c44bbaa) fix(tinytorch/announcement): restore unified ecosystem template ### 📊 Changes **1 file changed** (+28 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `tinytorch/quarto/config/announcement.yml` (+28 -4) </details> ### 📄 Description ## Summary The TinyTorch announcement bar was reverted during the v0.1.10 publish merge (commit \`0009f55a9\` on 2026-04-22) from the unified 4-line template shipped in PR #1505 back to a single-line release notice: \`\`\` 🎉 v0.1.10 released — v0.1.10 (retry after TINYTORCH_SITE path fix) · See release → \`\`\` Restores to the template used by all eight other Quarto sites (and the StaffML React banner). ## What the bar now says \`\`\` 🔥 TinyTorch — build your own ML framework from scratch; the companion framework to the textbook. [Start building →] 📘 The book: [Vol I: Foundations] · [Vol II: At Scale] — open access, free forever. 🛠️ Alongside the book: Hardware Kits (deploy) · MLSys·im (simulate) · Labs (explore) 📬 Newsletter: ML Systems insights & updates — [Subscribe →] \`\`\` Also: - \`type: info\` → \`type: primary\` (matches the eight sibling bars' color) - adds \`icon: megaphone\` + \`position: below-navbar\` to match the shared schema - file header now documents the reversion so a future release publish doesn't silently overwrite again ## Why not keep a release notice - Single-line + \`type: info\` breaks visual consistency with the other eight Quarto bars - "retry after TINYTORCH_SITE path fix" is commit-message-ese, not user-facing copy - Release news persists long after the release — "v0.1.10" is already stale-sounding and will look abandoned when v0.1.11 ships If a release ever genuinely needs a top-of-bar mention, the clean way is an optional \`release_note\` field on the shared schema that auto-expires — not overwriting the ecosystem-navigation copy. ## Test plan - [x] YAML parses cleanly (4 content lines, \`type: primary\`, \`dismissable: true\`, \`position: below-navbar\`) - [x] All pre-commit hooks passed - [ ] Post-merge: preview deploy on tinytorch site and visually confirm bar matches vol1/vol2/kits/etc. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-03 01:25:07 -05:00

GiteaMirror closed this issue

2026-05-03 01:25:08 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#9178