v0.2.1

Product-surface rewrite release.\n\nHighlights:\n- redesign README to be cleaner and more user-oriented\n- rewrite ClawHub-facing listing metadata around Shopify user value and common tasks\n- remove maintainer-facing roadmap language from the main product surfaces\n

v0.2.0

Usability and deployment release.\n\nHighlights:\n- add smoother post-setup usage examples for show store info, list products, and get product by title or id\n- add find-products and get-product --title support\n- add a canonical host installer helper script\n- upgrade the sidecar compose example into a more plug-and-play starter with a dedicated guide\n

v0.1.9

Runtime secret-safety hardening release.\n\nHighlights:\n- guided setup now writes a runtime .gitignore for .env, state/, and logs/\n- doctor now checks whether runtime .gitignore secret protection is present\n- docs now surface secret-handling guidance earlier and more explicitly\n

v0.1.8

Secret-handling hardening release.\n\nHighlights:\n- guided setup now steers secret entry into .env by default\n- docs explicitly keep SHOPIFY_API_KEY, SHOPIFY_API_SECRET, and SHOPIFY_ACCESS_TOKEN in .env only\n- public examples no longer encourage passing secrets as CLI flags\n- setup/doctor output now explains local secret handling more clearly\n

v0.1.7

Metadata alignment release.\n\nHighlights:\n- tighten ClawHub-facing skill metadata to match the guided low-friction setup positioning\n- keep GitHub and ClawHub versions aligned after the v0.1.6 productization release\n

v0.1.6

Guided setup and productization release.\n\nHighlights:\n- add a guided setup flow with setup-runtime.mjs guided-setup\n- polish doctor diagnostics with placeholder, callback, and Tailscale readiness checks\n- add first-run success transcript/screenshot artifacts\n- rewrite the README and setup flow around a canonical low-friction install -> setup -> done path\n\nWhat this improves:\n- faster first-run setup\n- clearer Shopify app values\n- clearer post-install validation\n- better adoption-facing documentation\n\nKnown limits:\n- Shopify app creation, credential entry, OAuth approval, and HTTPS ingress still require operator action\n- the skill remains intentionally narrow and security-first\n

v0.1.4

openclaw-shopify-manager v0.1.4

Changes

• set the GitHub repository homepage to the public project page
• added a visible Project links section near the top of the README
• kept the ClawHub homepage link path aligned through the skill metadata

Project page:
https://dave8172-website.vercel.app/projects/openclaw-shopify-manager

v0.1.3

openclaw-shopify-manager v0.1.3

Changes

• added the public project page to the skill homepage metadata
• added the project page link to the GitHub README
• kept GitHub as source of truth and ClawHub as distribution only

Project page:
https://dave8172-website.vercel.app/projects/openclaw-shopify-manager

v0.1.2

openclaw-shopify-manager v0.1.2

This release fixes the remaining ClawHub review inconsistencies while keeping GitHub as the source of truth and ClawHub as distribution only.

Changes

• added explicit skill metadata for Shopify env requirements and primary credential
• clarified that SHOPIFY_ACCESS_TOKEN is generated after OAuth and is not a required pre-install secret
• replaced the referenced systemd asset with assets/shopify-connector.service.txt so the published registry manifest retains it consistently
• removed the curl | sh Tailscale installation example and now point users to official OS-specific install docs

Why

ClawHub's review was still flagging the skill because the package did not declare expected env requirements and referenced a service asset name that was not retained consistently in the registry manifest.

v0.1.1

openclaw-shopify-manager v0.1.1

This release keeps ClawHub distribution aligned with the canonical GitHub repo and removes installer-style helpers from the published skill package.

Changes

• removed scripts/shopify-systemd.sh from the packaged skill
• removed scripts/install-runtime.sh from the packaged skill
• changed systemd guidance to documentation-only setup using the bundled service template
• kept the Shopify connector runtime and Tailscale checker in the skill package

Why

These helper scripts were causing the ClawHub security scan to flag the skill as suspicious. The skill now ships the minimum runtime and documentation needed for safe distribution.

Notes

• GitHub remains the source of truth
• ClawHub is used only for distribution of tagged releases
• manual systemd setup is still documented in references/systemd.md