ENG-1943 Update Roam to version 0.22.0#1152
Conversation
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| { | ||
| "name": "roam", | ||
| "version": "0.21.0", | ||
| "version": "0.22.0", |
There was a problem hiding this comment.
🚩 Post-submission version bump bundled with changelog
The apps/roam/RELEASE.md:19-26 release process states that the post-submission package bump to the next version "must happen after roam-release.yaml runs, because that workflow reads apps/roam/package.json for the version being sent to Roam" and should be done "in a follow-up PR." This PR bundles the 0.21.0 changelog with the bump to 0.22.0 in a single PR. If the roam-release.yaml workflow has not yet been triggered for 0.21.0, merging this PR first would cause the workflow to read 0.22.0 from apps/roam/package.json:3 instead of 0.21.0, resulting in incorrect version metadata in Linear, PostHog source maps, and Roam Depot. The previous release cycle kept these separate (commit c51cd7f4 for changelog, f845cb5a for bump). If the workflow has already been run, this is fine.
Was this helpful? React with 👍 or 👎 to provide feedback.
| - **Build metadata includes the commit SHA** - Release builds now stamp version metadata with the build commit, and branch builds keep the date/branch/commit format. | ||
| - **Per-install Roam extension version telemetry** - Extension load analytics now include per-install version metadata to help debug Roam app dev URL caching. |
There was a problem hiding this comment.
🚩 Changelog includes build-only and telemetry-only items
The apps/roam/RELEASE.md:43-45 guidance says "Internal chores, release-process tasks, telemetry-only work, and build-only work should usually stay out of the public changelog." Two of the five entries in the new 0.21.0 changelog section appear to fall into these categories:
- "Build metadata includes the commit SHA" (build-only)
- "Per-install Roam extension version telemetry" (telemetry-only)
The word "usually" provides flexibility, and the team may have decided these are user-relevant, but it's worth confirming intentionality.
Was this helpful? React with 👍 or 👎 to provide feedback.
1 participant
Uh oh!
There was an error while loading. Please reload this page.