Repository navigation
docs: prepare the 0.7.0 release - #34
Merged
Merged
Conversation
Move the Unreleased changelog entries to 0.7.0 with upgrade notes and comparison links, record the live checks for the token refresh fix and email certificate reuse in the session notes, and update the release checklist's candidate note.
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
Release notes and records for v0.7.0, following the release checklist. There are no code changes. Since v0.6.0,
mainhas gained:line login(issue bug: 🐛 Token refresh rejected (HTTP 400, gateway 10201) 3–4 days after QR login, well before the ~7-day boundary #29).--require-pinoption (issue feat: ✨ Reuse the saved certificate on email login so a known device can skip the PIN #31).Version 0.7.0 rather than 0.6.1, because #33 adds an option and changes email login's default; the checklist uses a minor version for that.
Changes
CHANGELOG.md: the Unreleased entries move to
0.7.0 - 2026-11-16, with a summary line and upgrade notes:line loginonceauthentication_failed, notremote_failed--require-pinopts out)The comparison links are updated.
docs/SESSION.md: both live results are recorded (details below).
docs/DEVELOPMENT.md: the checklist's "this candidate" note now covers 0.7.0.
Live checks (one account, macOS arm64)
line whoamiabout every 6 hours. 35 checks over 168 hours, none failed, including the 3–4 day point where v0.6.0 failed. Only command success was logged, not individual refreshes.0cb502d: the first email login asked for the PIN and saved a certificate. The second sent it and signed in without a PIN.whoamianddoctorpassed afterwards (one saved key loads), and recent Letter Sealing messages decrypted. Not observed: whether that reply carried a keychain or the checked saved key was reused. LINE's reply to a stale certificate is still uncaptured.Validation
At this branch on macOS arm64 with Go 1.27.4:
./scripts/check-toolchain.sh, goimports, gofmt,go vet, staticcheck,git diff --check.go test -race ./internal/... ./cmd/line ./pkg/line/... ./pkg/e2eeandgo test ./pkg ./pkg/ltsm.sh -n scripts/install-release.sh,./build.sh,./bin/line help../scripts/security-check.sh ./bin/line: 0 reachable vulnerabilities in the source and binary scans.Remaining release steps
v0.7.0tag on the merge commit. Pushing it publishes the GitHub release.kongesque/tap, andline update --check.Known issue, not a release blocker:
Runner.KeyLoadpanics on a malformed saved key. It predates this release and should be fixed separately.