Repository navigation
Install from the CI build; the artifact is the unpacked extension; version line in the popup - #28
Merged
Conversation
There are no tagged releases, so the README's 'releases page' step led nowhere. README, USAGE and the site now point at the latest successful CI build of main and its podkey-extension artifact, with the update path (same folder keeps the key; a different folder starts a fresh Podkey). CI uploads the staged extension folder instead of a zip: GitHub zips an artifact once, so the download unzips straight to the folder Chrome loads rather than to another zip. The completeness check runs on that folder. Co-Authored-By: jjohare <github@thedreamlab.uk>
jjohare
changed the title
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
1 participant
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.
There are no tagged releases, so the README's "download from the releases page" step led nowhere. Install now points at the build CI already makes, and the popup shows which build you have.
podkey-extensionartifact from the latest successful build ofmain. You need to be signed in to GitHub, and each build is kept for 90 days. The update path is spelled out: replace the contents of the same folder and your key is kept, but loading a different folder starts a fresh Podkey with no key..zip. GitHub zips an artifact once, so the download unzips straight to the folder Chrome loads, instead of to another zip. The completeness check from sidestr browser signer (window.nostr.sidestr.signTransaction), security-key fixes, 0.0.9 #27 now runs on that folder.v0.0.9 · 2cf8fe8at its foot, with the full commit and build time on hover. Every CI build ofmainshares the manifest version, so CI stampsbuild.jsonwith the commit it built (the PR head on a pull request). A source build shows the version alone.The version line was checked by rendering the built popup in Chrome at popup size.
npm testpasses 218/218 and lint is clean.🤖 Generated by Claude Code