Symbol set version displayed incorrectly despite correct app version being uploaded
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Bug Description
When uploading source maps with a full timestamp-based version string (e.g., 2026.02.230940), the Release correctly reflects the uploaded version. However, the associated symbol set version is shown incorrectly – it appears truncated to only the date portion (e.g., 2026.02.23), without the time component.
This mismatch prevents errors from being correctly associated with the right symbol set, meaning stack traces are not resolved and errors show "No stacktrace available."
We are using Vue/Vite with @posthog/rollup-plugin for source map uploads, configured with deleteAfterUpload: true.
How to reproduce
- Configure @posthog/rollup-plugin in Vite with a full timestamp-based version string (e.g., 2026.02.230940).
- Build and upload source maps – the upload completes successfully.
- Navigate to the Release in PostHog – the release version displays correctly (full timestamp).
- Check the associated symbol set – the version shown is truncated to the date only (e.g., 2026.02.23), not the full version string.
Additional context
The truncation of the version string in the symbol set appears to be where the mismatch originates, causing source maps to fail to associate with errors.
PostHog Cloud project: /error_tracking
Stack: Vue 3 / Vite / @posthog/rollup-plugin
Debug info
2026-02-23T15:41:21.538095Z INFO posthog_cli::utils::auth: Using token from env var, for environment 251311
2026-02-23T15:41:21.539168Z INFO posthog_cli::sourcemaps::inject: injecting selection: ["/home/runner/work/app/app/dist/assets/analytics-DWuIMmQ-.js", "/home/runner/work/app/app/dist/assets/editor-DU_BcPjV.js", "/home/runner/work/app/app/dist/assets/emoji-DdCA225e.js", "/home/runner/work/app/app/dist/assets/firebase-bAdmQw7k.js", "/home/runner/work/app/app/dist/assets/lodash-DOP3yL5f.js", "/home/runner/work/app/app/dist/assets/model-viewer-DfFx2YaI.js", "/home/runner/work/app/app/dist/assets/search-CtatEIwP.js", "/home/runner/work/app/app/dist/assets/ui-tUP_F4uk.js", "/home/runner/work/app/app/dist/assets/utils-16F9HEdR.js", "/home/runner/work/app/app/dist/assets/vendor-v93vAZla.js", "/home/runner/work/app/app/dist/assets/vidstack-D8eCD4pb.js", "/home/runner/work/app/app/dist/assets/index-DUpNMIGg.js", "/home/runner/work/app/app/dist/assets/Analytics-BMyO3Jhn.js", "/home/runner/work/app/app/dist/assets/Announcement-BCMRXGj5.js", "/home/runner/work/app/app/dist/assets/Announce
2026-02-23T15:41:21.601021Z INFO posthog_cli::sourcemaps::source_pairs: found 116 pairs
2026-02-23T15:41:22.050580Z WARN posthog_cli::api::releases: release app@2026.02.230940 not found
2026-02-23T15:41:22.215638Z INFO posthog_cli::api::releases: Release app@2026.02.230940 created successfully! 019c8b29-8d6c-0000-85e1-dc10325cd675
2026-02-23T15:41:22.485525Z INFO posthog_cli::sourcemaps::inject: injecting done
2026-02-23T15:41:22.519898Z INFO posthog_cli::sourcemaps::source_pairs: found 116 pairs
2026-02-23T15:41:22.519930Z INFO posthog_cli::sourcemaps::plain::upload: Found 116 chunks to upload
2026-02-23T15:41:22.686787Z INFO posthog_cli::api::releases: found release app@2026.02.230940
2026-02-23T15:41:22.720082Z INFO posthog_cli::api::symbol_sets: Starting upload of batch 0, 50 symbol sets
2026-02-23T15:41:22.933045Z INFO posthog_cli::api::symbol_sets: Server returned 50 upload keys (0 skipped as already present)
2026-02-23T15:41:26.726913Z INFO posthog_cli::api::symbol_sets: Starting upload of batch 1, 50 symbol sets
2026-02-23T15:41:26.956185Z INFO posthog_cli::api::symbol_sets: Server returned 50 upload keys (0 skipped as already present)
2026-02-23T15:41:29.805557Z INFO posthog_cli::api::symbol_sets: Starting upload of batch 2, 16 symbol sets
2026-02-23T15:41:30.053154Z INFO posthog_cli::api::symbol_sets: Server returned 16 upload keys (0 skipped as already present)
2026-02-23T15:41:31.171354Z INFO posthog_cli::invocation_context: Finishing up....
2026-02-23T15:41:31.171392Z INFO posthog_cli::invocation_context: Finished!
2026-02-23T15:41:31.171396Z INFO posthog_cli: All done, happy hogging!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the upload flow through posthog_cli::api::symbol_sets and compare the version passed there with the release handling in posthog_cli::api::releases. Reproduce the upload using @posthog/rollup-plugin with version 2026.02.230940, then verify that the symbol set retains the full version and associates source maps with the release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, vite
- Domain
- observability, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100