chore(release): 1.0.1
Exactly the two files a patch touches — package.json's version and CHANGELOG.md, section plus the link references at the bottom. wxt.config.ts declares no version key, so it must not appear in this diff, and it does not; the built manifest reads 1.0.1 and `npm run zip` emits bookmarkmagic-1.0.1-chrome.zip. `npm run verify:full` green: lint, svelte-check + tsc, knip, the grep gate, 694 tests, core coverage 97.4%/92.1%, the build, and check:manifest against the built artifact. The built manifest is byte-identical to the pre-phase baseline — same permissions, same key set — across ten commits and a WXT major-slot bump. The changelog is written for users rather than for the diff: what changed for someone who already has this installed, and the fact that they need do nothing. ⚠️ Stops here, deliberately. The tag and the store upload are human steps: git tag -s v1.0.1 && git push origin v1.0.1 and then docs/13 §1b from step 5 — which begins with the manual QA pass, including the 1.0.0 → 1.0.1 upgrade over an existing profile that nothing here can perform. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
3 files changed
+48
-4
No files matched your search
+46
-2
@@ -13,9 +13,52 @@ breaking format or schema changes (a BM JSON version bump).
|
||||
|
||||
Nothing yet.
|
||||
|
||||
## [1.0.1] — 2026-08-03
|
||||
|
||||
Stabilization, from the first pass over the shipped extension. No new features,
|
||||
no change to permissions, and nothing you have to do — Chrome updates itself.
|
||||
|
||||
### Fixed
|
||||
|
||||
- If the browser refuses part of an import, the report now says how many
|
||||
bookmarks were actually created, and — after a "replace everything" — names
|
||||
the safety backup so you can restore. It used to say only that something went
|
||||
wrong, while the items it had already written sat in your tree uncounted.
|
||||
- Cancelling a "replace everything" after the deletion had begun said only how
|
||||
many items were created, on a browser that was nearly empty. It now says what
|
||||
happened and points at your backup.
|
||||
- The import screen no longer offers a backup filename in the cases where no
|
||||
backup was written.
|
||||
- Pressing the browser's Back button during an import used to leave the manager
|
||||
permanently stuck — every tab disabled, and no way out but closing it.
|
||||
Navigation is now refused while an import is running, with an explanation.
|
||||
- Two manager tabs no longer overwrite each other's settings, and accepting the
|
||||
terms in one tab now unlocks the other.
|
||||
- Errors in the Edit and Export tabs appear in your own language again, with the
|
||||
browser's own message kept separately for bug reports.
|
||||
- Clearing the search box no longer leaves every folder it opened expanded, and
|
||||
collapsing a folder while searching now stays collapsed.
|
||||
- "Keep the first of each" no longer offers to delete bookmarks managed by your
|
||||
organisation, which the browser always refused, and says how many copies it
|
||||
removed if it stops early.
|
||||
- A profile with no writable bookmark folder now says so, instead of reporting a
|
||||
refused operation.
|
||||
|
||||
### Added
|
||||
|
||||
- The import screen states that imported bookmarks carry today's date — the
|
||||
browser does not let an extension set the original one. Your exported files
|
||||
still keep the real dates.
|
||||
- A link to the Chrome Web Store listing in the About tab.
|
||||
- Bug-report forms, a contributing guide, and `scripts/sanitize-bookmarks.mjs`,
|
||||
which strips every address and title from a bookmark file while keeping the
|
||||
structure a parsing bug depends on — so a sample can be attached to a public
|
||||
issue without publishing your browsing history.
|
||||
|
||||
## [1.0.0] — 2026-07-26
|
||||
|
||||
First public release.
|
||||
First public release. Approved by the Chrome Web Store and available to install
|
||||
from 2026-08-03.
|
||||
|
||||
### Added
|
||||
|
||||
@@ -44,5 +87,6 @@ First public release.
|
||||
- Parsing is bounded: 25 MB per file, 100 000 nodes, 200 levels of nesting.
|
||||
- No network access of any kind at runtime, enforced by a grep gate in CI.
|
||||
|
||||
[Unreleased]: https://github.com/poli0981/bookmarkmagic/compare/v1.0.0...HEAD
|
||||
[Unreleased]: https://github.com/poli0981/bookmarkmagic/compare/v1.0.1...HEAD
|
||||
[1.0.1]: https://github.com/poli0981/bookmarkmagic/compare/v1.0.0...v1.0.1
|
||||
[1.0.0]: https://github.com/poli0981/bookmarkmagic/releases/tag/v1.0.0
|
||||
+1
-1
@@ -21,7 +21,7 @@ Build-phase breakdown lives in `CLAUDE.md` (single source for sequencing).
|
||||
| 5 — Hardening + release prep | ✔ 2026-07-26 | contrast tokens + a test that enforces them, `EditTab` split under the hard limit, CHANGELOG + README, four CI callers, T1–T8 pass, clean-room `wxt zip` |
|
||||
| **v1.0.0 released** | ✔ 2026-07-26 | signed tag, GitHub Release with a `sha256sum -c`-verified zip, submitted to the Chrome Web Store |
|
||||
| **v1.0.0 published** | ✔ by 2026-08-03 | approved by CWS review with no rejection recorded; listing public, item id `eghnciphhegekmnofffpgbdfefckdhmg`, **real users installed** |
|
||||
| 6 — Post-launch stabilization | in progress 2026-08-03 | doc reconciliation, user-intake machinery, the defects below, dependency bumps → v1.0.1 |
|
||||
| 6 — Post-launch stabilization | ✔ 2026-08-03 | doc reconciliation, user-intake machinery, the defects below, dependency bumps → v1.0.1 |
|
||||
|
||||
**Verified on real browsers 2026-07-25:** Chrome and Brave, unpacked build.
|
||||
Until that point every phase had been tested only against a hand-rolled
|
||||
|
||||
+1
-1
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "bookmarkmagic",
|
||||
"private": true,
|
||||
"version": "1.0.0",
|
||||
"version": "1.0.1",
|
||||
"type": "module",
|
||||
"description": "Import, export & edit bookmarks between browsers — offline, no account, no cloud.",
|
||||
"license": "GPL-3.0-or-later",
|
||||
|
||||
Reference in new issue
Block a user