v0.5.0: Roam API 2026-07-07 envelope, auth errors, chat.message - #47
Merged
Conversation
Bumps package.json (and lockfile) to 0.5.0. Since v0.4.3: - Pin ROAM_API_VERSION to 2026-07-07 and unwrap the common v1 webhook envelope - Parse v0/v1 error bodies; permanent fail on token_revoked/invalid_token - Ignore chat.message edits/deletes for agent dispatch (#46)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release
Cuts v0.5.0 (minor). Bumps
package.json/package-lock.jsonfrom0.4.3→0.5.0.Changes since v0.4.3
ROAM_API_VERSION, unwrap the common v1 webhook envelope ({type,eventId,timestamp,apiVersion,data}) while still accepting bare baseline payloads, parse v0/v1 error codes with permanent auth failure ontoken_revoked/invalid_token, and ignorechat.messageedit/delete for agent dispatch.After merge
git tag v0.5.0 && git push origin v0.5.0v0.5.0(triggers thereleaseworkflow → npm publish with provenance).