Tags: gavinh2016/worldmonitor
Tags
chore(sdk/go): bump Version to 0.1.1 — publish-go tag guard (koala73#… …4888) The sdk/go/v0.1.1 publish failed its version-parity guard: the MIT relicense (koala73#4882) bumped npm/PyPI/gem versions but missed the Version const in worldmonitor.go (the workflow checks it against the tag). The tag will be re-pointed at this commit. Claude-Session: https://claude.ai/code/session_016LG2b5W6EH7mEGSxuRGUry
feat(sdk): official Python, Ruby, and Go SDK packages (orank multi-la… …nguage SDK gap, koala73#4816) (koala73#4817) orank docks 2 of 3 Access points because the official SDK exists only on npm. Ship zero-dependency, MCP-first client libraries — same design as the worldmonitor npm CLI (curated tool helpers + call_tool + REST escape hatch, WAF-safe User-Agent, env-var config, SSE-aware body parsing) — in three more ecosystems, each with homepage metadata on worldmonitor.app (how agents verify a package is the official SDK): - sdk/python → PyPI `worldmonitor-sdk` (canonical name is squatted by an unrelated 2023 package); publish-python.yml on py-v* tags via PyPI OIDC trusted publishing + attestations - sdk/ruby → gem `worldmonitor` (canonical name grabbed); publish-ruby.yml on gem-v* tags via rubygems/configure-rubygems-credentials OIDC - sdk/go → submodule github.com/koala73/worldmonitor/sdk/go; publish-go.yml on sdk/go/v* tags vets the module and warms proxy.golang.org so pkg.go.dev indexes the version Each SDK ships offline unit tests (18 py / 16 rb / 11 go), and tests/sdk-packages.test.mjs guards the version sync (manifest + source constant, cross-checked against release tags by the workflows) and the product-domain homepage metadata. Docs: /docs/sdks page, llms.txt + api/llms.txt advertisements, ARCHITECTURE CI table rows. Publishing needs a one-time pending-trusted-publisher setup on pypi.org and rubygems.org (documented in koala73#4816) before tagging py-v0.1.0, gem-v0.1.0, and sdk/go/v0.1.0. Claude-Session: https://claude.ai/code/session_01DJicKa3VSq7iwMk3E5nYyk
feat(licensing): MIT for the thin client packages — CLI + Python/Ruby… …/Go SDKs (koala73#4882) Owner decision (Elie, 2026-07-05): the four official thin clients are now MIT so any application can embed them without copyleft obligations — they are doorways to the API; anyone running or forking the PLATFORM still needs the AGPL server license, which is unchanged (root LICENSE, dashboard, server all stay AGPL-3.0-only). Also the only controllable lever on Socket.dev's License score (70, yellow, AGPL-flagged) for pkg:npm/worldmonitor. - cli/, sdk/python/, sdk/ruby/, sdk/go/: LICENSE → MIT; metadata license fields flipped; README license lines state the MIT-client/AGPL-platform split explicitly. - Version bumps for republish with corrected metadata: npm 0.1.3 (package.json + core.mjs VERSION, guard-paired), PyPI 0.1.1 (pyproject + __version__), gem 0.1.1. Go needs no file bump — pkg.go.dev reads sdk/go/LICENSE at the next tag. - Guard tests updated (cli-package, sdk-packages ×2); docs/license.mdx gains an explicit MIT-clients exception section (license-docs suite still green — AGPL platform positions untouched). Post-merge: push tags cli-v0.1.3, py-v0.1.1, gem-v0.1.1, sdk/go/v0.1.1 to republish via the OIDC workflows. Claude-Session: https://claude.ai/code/session_016LG2b5W6EH7mEGSxuRGUry
feat(sdk): official Python, Ruby, and Go SDK packages (orank multi-la… …nguage SDK gap, koala73#4816) (koala73#4817) orank docks 2 of 3 Access points because the official SDK exists only on npm. Ship zero-dependency, MCP-first client libraries — same design as the worldmonitor npm CLI (curated tool helpers + call_tool + REST escape hatch, WAF-safe User-Agent, env-var config, SSE-aware body parsing) — in three more ecosystems, each with homepage metadata on worldmonitor.app (how agents verify a package is the official SDK): - sdk/python → PyPI `worldmonitor-sdk` (canonical name is squatted by an unrelated 2023 package); publish-python.yml on py-v* tags via PyPI OIDC trusted publishing + attestations - sdk/ruby → gem `worldmonitor` (canonical name grabbed); publish-ruby.yml on gem-v* tags via rubygems/configure-rubygems-credentials OIDC - sdk/go → submodule github.com/koala73/worldmonitor/sdk/go; publish-go.yml on sdk/go/v* tags vets the module and warms proxy.golang.org so pkg.go.dev indexes the version Each SDK ships offline unit tests (18 py / 16 rb / 11 go), and tests/sdk-packages.test.mjs guards the version sync (manifest + source constant, cross-checked against release tags by the workflows) and the product-domain homepage metadata. Docs: /docs/sdks page, llms.txt + api/llms.txt advertisements, ARCHITECTURE CI table rows. Publishing needs a one-time pending-trusted-publisher setup on pypi.org and rubygems.org (documented in koala73#4816) before tagging py-v0.1.0, gem-v0.1.0, and sdk/go/v0.1.0. Claude-Session: https://claude.ai/code/session_01DJicKa3VSq7iwMk3E5nYyk
feat(licensing): MIT for the thin client packages — CLI + Python/Ruby… …/Go SDKs (koala73#4882) Owner decision (Elie, 2026-07-05): the four official thin clients are now MIT so any application can embed them without copyleft obligations — they are doorways to the API; anyone running or forking the PLATFORM still needs the AGPL server license, which is unchanged (root LICENSE, dashboard, server all stay AGPL-3.0-only). Also the only controllable lever on Socket.dev's License score (70, yellow, AGPL-flagged) for pkg:npm/worldmonitor. - cli/, sdk/python/, sdk/ruby/, sdk/go/: LICENSE → MIT; metadata license fields flipped; README license lines state the MIT-client/AGPL-platform split explicitly. - Version bumps for republish with corrected metadata: npm 0.1.3 (package.json + core.mjs VERSION, guard-paired), PyPI 0.1.1 (pyproject + __version__), gem 0.1.1. Go needs no file bump — pkg.go.dev reads sdk/go/LICENSE at the next tag. - Guard tests updated (cli-package, sdk-packages ×2); docs/license.mdx gains an explicit MIT-clients exception section (license-docs suite still green — AGPL platform positions untouched). Post-merge: push tags cli-v0.1.3, py-v0.1.1, gem-v0.1.1, sdk/go/v0.1.1 to republish via the OIDC workflows. Claude-Session: https://claude.ai/code/session_016LG2b5W6EH7mEGSxuRGUry
feat(sdk): official Python, Ruby, and Go SDK packages (orank multi-la… …nguage SDK gap, koala73#4816) (koala73#4817) orank docks 2 of 3 Access points because the official SDK exists only on npm. Ship zero-dependency, MCP-first client libraries — same design as the worldmonitor npm CLI (curated tool helpers + call_tool + REST escape hatch, WAF-safe User-Agent, env-var config, SSE-aware body parsing) — in three more ecosystems, each with homepage metadata on worldmonitor.app (how agents verify a package is the official SDK): - sdk/python → PyPI `worldmonitor-sdk` (canonical name is squatted by an unrelated 2023 package); publish-python.yml on py-v* tags via PyPI OIDC trusted publishing + attestations - sdk/ruby → gem `worldmonitor` (canonical name grabbed); publish-ruby.yml on gem-v* tags via rubygems/configure-rubygems-credentials OIDC - sdk/go → submodule github.com/koala73/worldmonitor/sdk/go; publish-go.yml on sdk/go/v* tags vets the module and warms proxy.golang.org so pkg.go.dev indexes the version Each SDK ships offline unit tests (18 py / 16 rb / 11 go), and tests/sdk-packages.test.mjs guards the version sync (manifest + source constant, cross-checked against release tags by the workflows) and the product-domain homepage metadata. Docs: /docs/sdks page, llms.txt + api/llms.txt advertisements, ARCHITECTURE CI table rows. Publishing needs a one-time pending-trusted-publisher setup on pypi.org and rubygems.org (documented in koala73#4816) before tagging py-v0.1.0, gem-v0.1.0, and sdk/go/v0.1.0. Claude-Session: https://claude.ai/code/session_01DJicKa3VSq7iwMk3E5nYyk
feat(licensing): MIT for the thin client packages — CLI + Python/Ruby… …/Go SDKs (koala73#4882) Owner decision (Elie, 2026-07-05): the four official thin clients are now MIT so any application can embed them without copyleft obligations — they are doorways to the API; anyone running or forking the PLATFORM still needs the AGPL server license, which is unchanged (root LICENSE, dashboard, server all stay AGPL-3.0-only). Also the only controllable lever on Socket.dev's License score (70, yellow, AGPL-flagged) for pkg:npm/worldmonitor. - cli/, sdk/python/, sdk/ruby/, sdk/go/: LICENSE → MIT; metadata license fields flipped; README license lines state the MIT-client/AGPL-platform split explicitly. - Version bumps for republish with corrected metadata: npm 0.1.3 (package.json + core.mjs VERSION, guard-paired), PyPI 0.1.1 (pyproject + __version__), gem 0.1.1. Go needs no file bump — pkg.go.dev reads sdk/go/LICENSE at the next tag. - Guard tests updated (cli-package, sdk-packages ×2); docs/license.mdx gains an explicit MIT-clients exception section (license-docs suite still green — AGPL platform positions untouched). Post-merge: push tags cli-v0.1.3, py-v0.1.1, gem-v0.1.1, sdk/go/v0.1.1 to republish via the OIDC workflows. Claude-Session: https://claude.ai/code/session_016LG2b5W6EH7mEGSxuRGUry
worldmonitor CLI v0.1.1 — first OIDC-published release (provenance)
PreviousNext