Skip to content

chore(extension): version 1.1.1, packaged only from main - #105

Merged
brgv-code merged 1 commit into
mainfrom
chore/extension-1.1.1
Nov 3, 2026
Merged

brgv-code merged 1 commit into
mainfrom
chore/extension-1.1.1

Conversation

@brgv-code

Copy link
Copy Markdown
Owner

The 1.1.0 in the Chrome Web Store does not have #100. Its zip was packaged from chore/extension-1.1.0 before #100 merged, so its manifest has no externally_connectable. jlog.ai's jlog:signed-in and jlog:signed-out messages are refused, send() reads that as "not installed", and the extension stays on whichever account it last had. Seen in practice: the extension on hello@bhargav.dev, the dashboard on the GitHub account.

  • Version 1.1.1, so the store accepts a build from main.
  • pnpm --filter @jlog/extension package now refuses unless the checkout is clean and HEAD is origin/main (it fetches first), and prints the commit it built. A zip from another branch could carry the right version number and miss what was merged under it, which is how 1.1.0 shipped.
  • It also refuses when the built manifest does not let the web base message the extension, since that is the one line the account sync depends on.

Checked on this branch: the packager refuses with uncommitted changes, then refuses again because HEAD is not origin/main. A plain vite build emits version 1.1.1 with externally_connectable: { matches: ["https://jlog.ai/*"] }. Extension tests (116) and typecheck pass.

After merging: run the packager on main, upload jlog-extension.zip, and once 1.1.1 is live, signing in or out on jlog.ai should move the extension with it.

@brgv-code
brgv-code merged commit 6a7d408 into main Nov 3, 2026
1 of 2 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