Repository navigation
chore: prepare the 0.2.0 release - #8
Merged
Merged
Conversation
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
3 of 5 tasks
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
…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>
4 of 5 tasks
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <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.
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.0section, 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 the0.1.0tag, and the new work is under## 0.2.0: mocked cookies, the narrow header with its empty-hosts warning, wrapping response tabs, theURLProtocol.taskfallback from fix: decide a task again where the OS has no URLProtocol.task getter #9, and theConfigurationStorerequirement.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 indocs/release-builds.mdand its Korean copy.script/prepare-releasechecks the manifest and the URL against the tag. The versions inscript/comments and in the release script's tests are examples, and are left alone.Verification log:
## 0.2.0 — not tagged yetentry, 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.0.1.0 — not tagged yetbecomes0.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.0notes 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-cliand the Necto window):HttpOnlynot rerun); the failed-discard banner was not seen.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.0section. See the summary.Agent interface
No change. The manifest's
versionfield moves to 0.2.0. No operation, binding version, input, output, error ormaplocal.statefield changes.Test Plan
script/ciexit 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.mdshows only added lines (the 0.2.0 section).script/prepare-release 0.2.0 <out>exits 0, and itsrelease-notes.mdholds only the 0.2.0 section.script/check-doc-pairsandscript/check-doc-linkspass.