Skip to content

feat: update dependencies#67

Merged
michaelklishin merged 1 commit intoruby-amqp:mainfrom
fretb:feature/hashie-5-update
Oct 23, 2025
Merged

feat: update dependencies#67
michaelklishin merged 1 commit intoruby-amqp:mainfrom
fretb:feature/hashie-5-update

Conversation

@fretb
Copy link
Copy Markdown
Contributor

@fretb fretb commented Oct 22, 2025

Updates dependencies to their latest version. Verified tests locally, all work.

Updates dependencies to their latest version. Verified tests locally,
all work.

Signed-off-by: Frederik Thuysbaert <frederik.thuysbaert@combell.group>
@michaelklishin michaelklishin merged commit f9f2344 into ruby-amqp:main Oct 23, 2025
@michaelklishin
Copy link
Copy Markdown
Member

@fretb thank you. How soon do you need a new release to be published to rubygems.org?

@fretb
Copy link
Copy Markdown
Contributor Author

fretb commented Oct 23, 2025

@fretb thank you. How soon do you need a new release to be published to rubygems.org?

Hi @michaelklishin, the sooner the better. I'm using this in combination with Cinc Client, which since the newest release has a conflicting dependency.

Thanks!

@fretb fretb deleted the feature/hashie-5-update branch October 23, 2025 05:17
@michaelklishin michaelklishin added this to the 3.1.0 milestone Oct 23, 2025
@fretb fretb mentioned this pull request Nov 4, 2025
fretb added a commit to fretb/rabbitmq_http_api_client that referenced this pull request Nov 5, 2025
In ruby-amqp#67, I proposed to update the dependency constraints to allow the gem
to be compatible with newer gem versions.

I now see that what I did was wrong, while no code changes were done
(meaning that the dependency constraints as they were would still work),
I made the gem conflict with working gem versions.

I updated the constraints to reflect what I was actually trying to do:
  Make it compatible with newer gem versions, not break compatibility
  with older working ones.

Signed-off-by: Frederik Thuysbaert <frederik.thuysbaert@combell.group>
fretb added a commit to fretb/rabbitmq_http_api_client that referenced this pull request Nov 5, 2025
In ruby-amqp#67, I proposed to update the dependency constraints to allow the gem
to be compatible with newer gem versions.

I now see that what I did was wrong, while no code changes were done
(meaning that the dependency constraints as they were would still work),
I made the gem conflict with working gem versions.

I updated the constraints to reflect what I was actually trying to do:
  Make it compatible with newer gem versions, not break compatibility
  with older working ones.

Signed-off-by: Frederik Thuysbaert <frederik.thuysbaert@combell.group>
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