release notes: the 1.3.0 entries the merged PRs did not leave behind - #94
Merged
Merged
Conversation
Deploying super-prototyping with
|
| 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 |
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
## Unreleasedhad 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):
<use>in the inspector, the Brand kit button and page, a picture has an address, thumbnails served at the size they are drawn.brand-kit, clone-prototype padding a glyph crop before tracing,refkit shoot --scaleas a float.tiktok-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
refkitsubcommand, a canvas feature". This window has a new skill and canvas features.imagesrows inlayout.jsonare additive, so not a major.Does not bump the version. After this merges:
Actions → Release →
1.3.0(must dispatch frommain; the workflow refuses a branch).On
release/1.3.0, the same edit as release 1.2.0 #72: leave## Unreleasedas the placeholder, insert## v1.3.0under it with this lede, so the grouped bullets fall under that heading:The tag job reads exactly
## v1.3.0. Merging without that heading falls back to generated notes.Merge. The tag
super-prototyping--v1.3.0and the GitHub Release follow.Checklist
ref-*.html,assets/refs/or other third-party captures are in this PR.gen.pywas edited and re-run, and theNN-*.htmlboards were not hand-edited.layout.json,probes.json,crops.jsonandassets.jsonare committed alongside the boards.README.mdand no folder has its own.gitignore.## UnreleasedinRELEASE-NOTES.md.canvas/changed:bun testandbun run buildpass incanvas/.Gates run locally on current
main(this PR is notes only):canvas/: oxlint, 95 tests, buildtools/: 25 refkit + 6 sp-canvas checksscripts/bump-version.sh --check: all 7 files at 1.2.0claude plugin validate . --strictand.claude-plugin/plugin.json --strict: passed