Skip to content

release notes: the 1.3.0 entries the merged PRs did not leave behind - #94

Merged
Jing-yilin merged 3 commits into
mainfrom
release-notes-1.3.0
Sep 15, 2026
Merged

Jing-yilin merged 3 commits into
mainfrom
release-notes-1.3.0

Conversation

@Jing-yilin

@Jing-yilin Jing-yilin commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

What this changes

## Unreleased had only the placeholder. A release cut from it would have published generated commit subjects, while 1.2.0..main is 84 commits including a new skill and several canvas features.

Reconstructed from the log and grouped the way the released sections are (same job as #71):

  • The canvas — inspect the board on the canvas (not a copy in the panel), fold and hide layers, sprite <use> in the inspector, the Brand kit button and page, a picture has an address, thumbnails served at the size they are drawn.
  • The toolkit and the skillsbrand-kit, clone-prototype padding a glyph crop before tracing, refkit shoot --scale as a float.
  • Example canvasestiktok-ios, x-ios, instagram-ios, perplexity-ios, and brand kits on thirteen canvases.

No code changes. This is the line each of those pull requests owed the file.

Version is 1.3.0, not a patch: CONTRIBUTING says minor is "a new skill, a new refkit subcommand, a canvas feature". This window has a new skill and canvas features. images rows in layout.json are additive, so not a major.

Does not bump the version. After this merges:

  1. Actions → Release1.3.0 (must dispatch from main; the workflow refuses a branch).

  2. On release/1.3.0, the same edit as release 1.2.0 #72: leave ## Unreleased as the placeholder, insert ## v1.3.0 under it with this lede, so the grouped bullets fall under that heading:

    ## v1.3.0
    
    YYYY-MM-DD. A product's published brand sits on the canvas next to its screens, as
    pictures you can link to, and the board you inspect is the one on the canvas
    rather than a copy in the panel. A fourth skill collects those pictures. Four
    more example canvases.
    

    The tag job reads exactly ## v1.3.0. Merging without that heading falls back to generated notes.

  3. Merge. The tag super-prototyping--v1.3.0 and the GitHub Release follow.

Checklist

  • No ref-*.html, assets/refs/ or other third-party captures are in this PR.
  • If a canvas folder changed: gen.py was edited and re-run, and the NN-*.html boards were not hand-edited.
  • If a canvas folder changed: layout.json, probes.json, crops.json and assets.json are committed alongside the boards.
  • Every new canvas folder has a README.md and no folder has its own .gitignore.
  • If a user would see this change: it has a line under ## Unreleased in RELEASE-NOTES.md.
  • If canvas/ changed: bun test and bun run build pass in canvas/.

Gates run locally on current main (this PR is notes only):

  • canvas/: oxlint, 95 tests, build
  • tools/: 25 refkit + 6 sp-canvas checks
  • scripts/bump-version.sh --check: all 7 files at 1.2.0
  • claude plugin validate . --strict and .claude-plugin/plugin.json --strict: passed

Unreleased was empty. Reconstruct it from #74#93 so the release job has a body to cut from.
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 15, 2026

Copy link
Copy Markdown

Deploying super-prototyping with  Cloudflare Pages  Cloudflare Pages

Latest commit: 938727c
Status: ✅  Deploy successful!
Preview URL: https://e945d71b.super-prototyping.pages.dev
Branch Preview URL: https://release-notes-1-3-0.super-prototyping.pages.dev

View logs

Jing-yilin and others added 2 commits September 15, 2026 15:10
The dated lede is step 4 of Cutting a release, added when the heading becomes
## v1.3.0. Putting it here would duplicate it, or land the placeholder in the
GitHub Release body.
…ures

The mark was changed to a palette while the notes were being written; the
code comment says why a picture frame was rejected.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Jing-yilin
Jing-yilin merged commit 87479f9 into main Sep 15, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant