fix: only create versions of records that changed in an upsert #205
Conversation
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
…ped records on upsert
barnabasJ
force-pushed
the
fix/handle-upsert-skipped-records
branch
from
8b73b77 to
2970322
Compare
barnabasJ
commented
Oct 2, 2025
| defp deps do | ||
| [ | ||
| {:ash, ash_version("~> 3.5")}, | ||
| {:ash, ash_version("~> 3.5 and >= 3.5.43")}, |
There was a problem hiding this comment.
It failed with the version that was installed. I updated to the latest one. I haven't looked into what exactly changed between the two versions.
This was referenced Oct 2, 2025
|
🚀 Thank you for your contribution! 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Contributor checklist
Leave anything that you believe does not apply unchecked.
extra context