Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not differentiate between native and non-native for refined #2268

Closed
wants to merge 1 commit into from

Conversation

hamnis
Copy link
Collaborator

@hamnis hamnis commented May 13, 2024

Use 0.11.1 for both

@hamnis hamnis requested a review from zarthross as a code owner May 13, 2024 07:45
@zarthross
Copy link
Member

@hamnis Is this not a binary breaking change for users of circe-refined?

The reason native use a newer version was because native required a newer version and did not exist when circe-refined was created, so in a way wasn't binary breaking.

@hamnis
Copy link
Collaborator Author

hamnis commented May 14, 2024

it might be, but do we have to be so strict with regards to binary breakage in a third party integration module?

If we are, we should spin it off into an own repo, which has its own release schedule.

@armanbilge
Copy link
Contributor

If we are, we should spin it off into an own repo, which has its own release schedule.

Agree. We should do this for all the circe integrations, same as we did for http4s.

@hamnis
Copy link
Collaborator Author

hamnis commented May 15, 2024

Closing for now. We will spin off refined into a separate repo

@hamnis hamnis closed this May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants