Require slack-ruby-client ~> 3.2 - #41
Open
romanoff wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Co-Authored-By: Amplify 3.0.1 <amplify@getjobber.com>
romanoff
marked this pull request as ready for review
August 4, 2026 22:42
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
1 participant
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.
What's in this PR?
Pins
slack-ruby-clientto~> 3.2in the gemspec (previously unconstrained) and bumps the gem version to 2.0.4, so consuming repos pick up the current Slack client by updating this library rather than pinning it themselves. This follows the review discussion on GetJobber/jobber-frontend#14346 — once this is released, jobber-frontend will move its git tag to v2.0.4 and drop the direct lockfile pin.One caveat worth knowing before release: Jobber (the monolith) consumes this gem at v2.0.2 and is stuck on
slack-ruby-client1.0.0 — every later release requires faraday 2, which Jobber can't take whileelasticsearch-transport(capped at 7.13.x by the prod AWS ES 7.10.2 OSS domain) requires faraday 1.x. With this constraint, Jobber stays on v2.0.2 until its legacy Elasticsearch stack migrates to OpenSearch. That's already the status quo; noting it so the constraint choice is deliberate.QA Instructions
slack-ruby-clientto 3.2.0; there are no dependency or API changes between 3.1.x and 3.2.0 that affect how this library posts to Slack.References
Co-Authored-By: Amplify 3.0.1 amplify@getjobber.com
🤖 Generated with Claude Code