Merged
Conversation
Member
|
I wonder if I should cut a release branch pinning the current version to the non broke ecto. |
Contributor
Author
I think that would be nice for people who want to stay on Ecto v3.12 and don't want to accidentally update in the future. For ecto_ch I deprecated the version (v0.6.1) that was too permissive But I think now deprecation might have been unnecessary ... |
warmwaffles
approved these changes
Jun 19, 2025
Member
|
Thanks for the work @ruslandoga. I'm gonna retire the prior release |
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.
closes #168