Repository navigation
✨ Feature: add browser SDK for PicGo Cloud - #1
Merged
Merged
Conversation
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.
Add
@picgo/cloud-sdk, a zero-runtime-dependency TypeScript SDK for third-party browser applications. Users provide their own PicGo Cloud token to upload files, list and inspect media, edit metadata, and delete individual or batches of media.The SDK provides progress reporting, pause/resume/cancel, persistent upload recovery, a required
MediaItem.urlfor every media type, typed errors, ESM output, and type declarations. English and Chinese documentation covers application integration and SDK usage. A local playground supportsPICGO_API_URLconfiguration through.env; its public examples use the standard PicGo Cloud API URL.Validation: TypeScript, ESLint, 53 SDK tests, 5 development/release tests, build, actionlint, package inspection, and npm publish dry-run passed. Browser checks covered uploads, recovery, media operations, and API error handling. Authenticated end-to-end testing against the live service remains pending.
Tag-triggered npm publishing uses Trusted Publishing (OIDC), validates tag/version and main-branch ancestry, and publishes the verified tarball with provenance. No package has been published by this work.
Release preparation uses
@picgo/bump-version3 with the PicGo commit convention, Commitizen, and commitlint hooks.pnpm release:drypreviews version/changelog changes;pnpm releaseprepares the release commit and tag for the existing npm workflow. Dependency installation, frozen-lockfile installation, commitlint configuration, and the no-mutation release preview were verified.