Skip to content

chore: prepare the 0.2.0 release - #8

Merged
ryan-son merged 14 commits into
mainfrom
release/0.2.0-prep
Oct 26, 2026
Merged

ryan-son merged 14 commits into
mainfrom
release/0.2.0-prep

Conversation

@ryan-son

@ryan-son ryan-son commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

Summary

Prepares the 0.2.0 release. The tag itself waits for the verification log's Necto rows.

  • The changelog put new work under the released 0.1.0. PRs Fix the header's first row in a narrow panel and fold the allowed hosts behind a button #3–fix: say "No allowed hosts" in the hosts' caption when there are none #7 added their lines to the ## 0.1.0 section, and fix: wrap response tabs instead of widening the editor #6 rewrote one of its sentences, so the published 0.1.0 notes no longer matched the file. The 0.1.0 section is restored byte for byte from the 0.1.0 tag, and the new work is under ## 0.2.0: mocked cookies, the narrow header with its empty-hosts warning, wrapping response tabs, the URLProtocol.task fallback from fix: decide a task again where the OS has no URLProtocol.task getter #9, and the ConfigurationStore requirement.

  • The version is 0.2.0 in Panel/public/manifest.json, the README package line (English and Korean), and the "Block a release in CI" download URL in docs/release-builds.md and its Korean copy. script/prepare-release checks the manifest and the URL against the tag. The versions in script/ comments and in the release script's tests are examples, and are left alone.

  • Verification log:

    • A ## 0.2.0 — not tagged yet entry, with the template's rows plus one row for each change in this release that was never measured in Necto (the hosts button and Esc, the empty-hosts warning, the response tabs, the toast order, the cookie rows after the restack, the cookie notice and banner, the log-out sentence, the badge sheet, and iOS 17.0–17.4 for fix: decide a task again where the OS has no URLProtocol.task getter #9). Every row reads "not verified yet". They are run on the release candidate before the tag.
    • The cookie entry from 2026-10-12 is renamed from "Unreleased" to "0.2.0: mocked cookie journal, on the archive build".
    • 0.1.0 — not tagged yet becomes 0.1.0 — 2026-10-05. Nothing links to these headings.
  • Necto 0.2.2. Rebased on chore: require Necto 0.2.2 and drop the registration order warning #11, which makes 0.2.2 the minimum. Necto 0.2.2 moved URLSession capture into its own product and stopped resending requests, so the registration order no longer matters. The ## 0.2.0 notes gain two lines for it: the new requirement and import, and the removed order warning. The examples pin 0.2.2. The verification entry names Necto 0.2.2 and records chore: require Necto 0.2.2 and drop the registration order warning #11's measurement.

  • Verification rows, run on the release candidate (Necto 0.2.2, iPhone SE (3rd generation) simulator on iOS 18.4, through necto-cli and the Necto window):

    • The run found a regression from chore: require Necto 0.2.2 and drop the registration order warning #11: the Traffic tab drew no list or detail. fix: give the traffic list and detail the flexible row again #12 fixed it, and the panel rows ran with that fix.
    • Pass: data from the app, disconnect and reconnect, dark, 13 and 16 pt, narrow and wide in both tabs, English and Korean, with and without the network plugin, empty hosts, ten response tabs, undo with the hosts open, the log-out confirmation's cookie sentence, cookie notice and discard.
    • Partial: the cookie rows (in use, set aside, reapplied and discarded pass; relaunch and HttpOnly not rerun); the failed-discard banner was not seen.
    • Not verified, with reasons in the log: a device over USB, light and the light/dark switch, iOS 17.0–17.4, and the badge sheet.
    • Found, not a 0.2.0 change: on a Home-button iPhone the status bar draws over the badge's text.

Between this merge and the tag, the README asks for from: "0.2.0", which doesn't resolve yet. Tag soon after merging.

Changelog

This PR writes the ## 0.2.0 section. See the summary.

Agent interface

No change. The manifest's version field moves to 0.2.0. No operation, binding version, input, output, error or maplocal.state field changes.

Test Plan

  • script/ci exit 0 on GitHub at chore: require Necto 0.2.2 and drop the registration order warning #11 and fix: give the traffic list and detail the flexible row again #12 (vitest 1101: 43 order-warning tests removed, one grid-row test added; Swift 91 + 131). This branch adds docs only on top of main; the embedded panel matches a fresh build.
  • git diff 0.1.0 -- CHANGELOG.md shows only added lines (the 0.2.0 section).
  • script/prepare-release 0.2.0 <out> exits 0, and its release-notes.md holds only the 0.2.0 section.
  • script/check-doc-pairs and script/check-doc-links pass.
  • The QuickStart example resolves Necto 0.2.2 ("Checking out 0.2.2 of package 'necto'").
  • Before tagging: fill the 0.2.0 Necto rows on the release candidate. The rows left unverified are listed in the log with their reasons.

The changes merged since 0.1.0 had been written into the released 0.1.0
section of the changelog. That section is back to what 0.1.0 shipped,
and the new work is under 0.2.0. The manifest, the README package line
and the release guide's download URL name 0.2.0, as prepare-release
requires.

The verification log gains a 0.2.0 entry whose Necto rows are still to
be run on the release candidate, and 0.1.0's heading carries its date.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HvfREejSbdqHNbZ87WYdW
ryan-son and others added 6 commits October 14, 2026 11:10
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HvfREejSbdqHNbZ87WYdW
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HvfREejSbdqHNbZ87WYdW
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HvfREejSbdqHNbZ87WYdW
Necto 0.2.1 changes only UI Control's touch injection (toss/necto#19);
NectoSDK, which this plugin uses, is the same. The package already
resolves 0.2.1 through upToNextMinor. The examples pinned exactly 0.2.0,
so the release checks now build them with what users get. design.md
says that its upstream references are to 0.2.0 and that none of the
cited files changed, and the 0.2.0 verification entry names Necto 0.2.1.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HvfREejSbdqHNbZ87WYdW
ryan-son and others added 4 commits October 27, 2026 00:07
…release/0.2.0-prep

# Conflicts:
#	Examples/QuickStart/QuickStart.xcodeproj/project.pbxproj
#	Examples/SeparateProject/Dev/Dev.xcodeproj/project.pbxproj
#	README-ko.md
#	README.md
#	docs/design-ko.md
#	docs/design.md
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
ryan-son and others added 3 commits October 27, 2026 00:56
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@ryan-son
ryan-son merged commit 270ba80 into main Oct 26, 2026
1 check 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