Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CI failing on deprecation warnings

Open
#409 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
ci-cd, testing

Research direction

Start with spec/slack/slack_spec.rb:35 and the linked CI run, then reproduce the deprecation output around the failing Slack globals test. Done means the test still checks the intended missing-token error, deprecation warnings no longer obscure it, and the CI check passes.

Written by the indexing model from the issue text.

Description

confirmed bug

Need to relax the test a bit to allow for deprecations, and fix the deprecations.

https://github.com/slack-ruby/slack-ruby-client/runs/6746428976?check_suite_focus=true

  1) Slack globals requires --slack-api-token
     Failure/Error:
       expect(err).to(
         start_with(
           'error: parse error: Set Slack API token via --slack-api-token or SLACK_API_TOKEN.'
         )
       )
     
       expected "Top level ::CompositeIO is deprecated, require 'multipart/post' and use `Multipart::Post::CompositeR...lack [global options] auth test \n\n\n\nDESCRIPTION\n    Checks authentication & identity. \n\n\n\n" to start with "error: parse error: Set Slack API token via --slack-api-token or SLACK_API_TOKEN."
     # ./spec/slack/slack_spec.rb:35:in `block (3 levels) in <top (required)>'
     # /Users/dblock/.rvm/gems/ruby-2.7.5/gems/webmock-3.14.0/lib/webmock/rspec.rb:37:in `block (2 levels) in <top (required)>'
Dominant language
Ruby
Stars
1.3k
Forks
222
Avg merge
1d 14h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from slack-ruby/slack-ruby-client

All issues in slack-ruby/slack-ruby-client

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.