Repository navigation
feat(automations): Record the Automation version on each run - #2212
Merged
Merged
Conversation
Store the version that a Scheduled or event automation run dispatched, so a reader can see which instruction ran and who saved it after later edits. Refs #2211 Co-Authored-By: David Cramer <david@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dcramer
approved these changes
Oct 23, 2026
This branch was successfully deployed
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.
After an Automation is edited, we could not tell which instruction an earlier run used, or who saved that instruction.
junior_automation_runsstored the Automation id, but not the version.This adds a nullable
automation_versioncolumn and a foreign key tojunior_automation_versions. When a run is dispatched, the column is set to the newest version whose stored definition equals the dispatched definition. That is the same rule the active version uses. Later writes, such as completion, keep the value.The definition is matched with jsonb equality, not "newest version", so an edit that lands between the dispatch and the run write does not get attributed to the wrong version.
First step of #2211.
via David Cramer.
--
View Junior Session [Sentry]