Skip to content

chore(release): v0.2.0 - #25

Merged
rendyuwu merged 3 commits into
mainfrom
dev
Oct 6, 2026
Merged

rendyuwu merged 3 commits into
mainfrom
dev

Conversation

@rendyuwu

@rendyuwu rendyuwu commented Oct 6, 2026

Copy link
Copy Markdown
Owner

What

Merges dev into main for v0.2.0.

Why

Tagging v0.2.0 on main runs .github/workflows/release.yml, which builds
the signed updates, the extension zips and a draft GitHub Release with notes
from the [0.2.0] section of CHANGELOG.md.

Included:

How

Merge commit, not squash, so dev's history lands on main unchanged.
main's only commits not on dev are the v0.1.0 and v0.1.1 merge commits,
and the v0.1.1 one's tree is dev's at #18, so the merge has nothing to
resolve: its tree is dev's head tree.

Testing

  • CI passed all seven checks on chore(release): prepare v0.2.0 #24, whose tree is the current dev head:
    frontend, rust, extension, and the macOS arm64, macOS x64, Linux x64 and
    Windows x64 bundles. The push run on fix(vault): let the join form follow the window and accept a blank Region #23's merge into dev passed too.

  • node scripts/release-notes.mjs v0.2.0 prints the 0.2.0 section and the
    macOS footer.

  • The version is 0.2.0 in package.json, extension/package.json,
    src-tauri/tauri.conf.json, src-tauri/Cargo.toml,
    src-tauri/subclave-proxy/Cargo.toml and both extension manifests.

  • pnpm exec tsc --noEmit clean

  • Manual smoke-test of the affected feature

  • (If you touched src-tauri/) cargo check clean

  • (If UI) tested in pnpm tauri:dev (isolated dev data dir)

CI covers the two checked boxes. This PR adds no code of its own.

Screenshots / GIFs

None. The UI changes are in #21 and #23, and neither has screenshots.

Notes for reviewer

…row (#21)

When the page's host has no entries of its own but other hosts of the
domain do, the picker's last row now opens the toolbar popup through
the service worker (`inline-open-popup`, `chrome.action.openPopup`). It
fills nothing and releases nothing, so it needs a trusted click but not
the six guards. Where the popup cannot open, the footer turns into text
naming the Extensions menu and the `fill-login` shortcut for the rest of
the page.

Closes #20.
…gion (#23)

The join screen was a fixed 384px column that scrolled on its own, so
the wheel worked only over that column. The eye button's addon in
PasswordField hung 3px past its input group, and the scrolling form
turned that into a horizontal scrollbar. The screen is now the scroll
container and the form is m-auto up to max-w-3xl, the Settings content
width. The addon overrides pr-3 has-[>button]:-mr-1 with
pr-2 has-[>button]:mr-0, so the button stays where it was and nothing
hangs past the group.

Join vault no longer requires an S3 Region. provider_config passes the
region through as typed, Settings > Sync saves it blank, and a server
that takes an empty one works with it (Cloudflare R2 reads it as auto).
Bucket stays required for S3: a blank one builds {endpoint}//{key}
paths.

connectionFieldsReady becomes missingConnectionFields, which returns the
labels of the blank fields, and useMasterPassword also returns problems,
one sentence per rule the password still fails. useJoinSync builds
blockers from both, the credential pair and the passphrase, and derives
canSubmit from it. The screen lists the blockers under the button in
muted text.

scripts/sync-verify.ts checks the new connection gate, including the
blank Region.

Closes #22
Version 0.2.0 everywhere it is set, and CHANGELOG.md holds the dated [0.2.0] section in place of [Unreleased] and [0.1.1].
@rendyuwu
rendyuwu merged commit 0c3b7b5 into main Oct 6, 2026
14 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