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

Test on Elixir 1.18 and NATS 2.10.24 #188

Merged
merged 1 commit into from
Jan 9, 2025
Merged

Conversation

davydog187
Copy link
Contributor

No description provided.

nats: "2.10.24"

- otp: "27"
elixir: "1.18"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't the main branch block below cover 1.18.* development? I've been in the habit of adding older versions once there's a new minor version under development. Do you think it's valuable to have 1.18 called out separately from the main?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it will cover development on the upcoming 1.19 release and any possible changes.

With that being said, I wouldn't personally test against main and would drop it in favor of the explicit 1.18

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To clarify my position here, I would advise testing against "nightly" builds such as main here, since they tend to have bugs and may introduce intermediate failures to CI.

For a library, it's better to keep the main CI against the latest stable releases.

If you want to test against main, I would do that outside of the PR cycle, possibly as a nightly test.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you're right. The main branch is probably too unstable to be part of our CI. I'll just remove it for now as we have a schedule monthly build which would check for all of the supported minor versions

@mmmries mmmries merged commit 813343d into nats-io:main Jan 9, 2025
5 checks passed
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.

2 participants