posthog/PostHog/upload-source-maps

Inject and upload sourcemaps with posthog-cli

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
directoryDirectory containing built assets (e.g., `dist`)yes
api-keyPostHog personal API key with error tracking write scope. See https://app.posthog.com/settings/user-api-keys#variablesyes
project-idPostHog project ID. See https://app.posthog.com/settings/project#variablesyes
release-nameRelease name. If not provided, the action tries to read the Git repository name. If it cannot determine a value, the action failsno
release-versionRelease version (e.g., commit SHA). If not provided, the action uses the current commit SHA. If it cannot determine a value, the action failsno
buildBuild number (e.g., 42, CFBundleVersion on iOS, versionCode on Android). Stored as release metadata.no
hostPostHog host URL. If you use the US cloud, you don't need to set this. For the EU cloud, set `https://eu.posthog.com`no
delete-after-uploadWhether to delete the source map files after uploading themnofalse
skip-ssl-verificationWhether to skip SSL verification when uploading chunks - only use when using self-signed certificates for self-deployed instancesnofalse
batch-sizeThe maximum number of chunks to upload in a single batch (default: 50)no
ignoreOne or more directory glob patterns to ignore (comma-separated)no
cli-versionPostHog CLI version to use (e.g., '0.5.29'). If not provided, the latest version is usednolatest

no outputs