Update API from slack-api-ref@3ec3c10

[github-actions]

Update API from slack-api-ref.
Rev: 3ec3c10
Date: 2025-02-08

[coveralls]

Pull Request Test Coverage Report for Build 13220174908

Details

• 109 of 122 (89.34%) changed or added relevant lines in 10 files are covered.
• 9 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.2%) to 89.348%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
lib/slack/web/api/endpoints/assistant_threads.rb	17	20	85.0%
lib/slack/web/api/endpoints/admin_conversations.rb	7	11	63.64%
lib/slack/web/api/endpoints/conversations_requestSharedInvite.rb	10	16	62.5%

Files with Coverage Reduction	New Missed Lines	%
lib/slack/web/api/endpoints/admin_users_session.rb	1	64.29%
lib/slack/web/api/endpoints/files.rb	8	45.45%

Totals
Change from base Build 13217187420:	-0.2%
Covered Lines:	5561
Relevant Lines:	6224

---

💛 - Coveralls

[gregsaab]

@dblock can this be merged in prior to file_upload_v2?

[dblock]

@gregsaab I usually do this one before every release, does it need to be?

For file upload v2 I think it's really a utility method that wraps calling an API and doing some more work. It's neither a mixin (something used in many places) nor a patch (something that changes an existing method), so maybe we need a new "helpers" folder/concept (open to other names)?

[gregsaab]

@gregsaab I usually do this one before every release, does it need to be?

For file upload v2 I think it's really a utility method that wraps calling an API and doing some more work. It's neither a mixin (something used in many places) nor a patch (something that changes an existing method), so maybe we need a new "helpers" folder/concept (open to other names)?

When considering the patch approach to adding this method, it seemed wise to have that merged in before making a patch. But, it's not necessary given helper approach.