[BUG] Various commands are not working in CI context since version `2.33.0`.

Open
#218 13 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
deno, go
Domain
cli

Research direction

No source files or tests are named. Start by reproducing the slack activity and slack datastore bulk-put commands in the reported Deno 2.2.2 AWS Lambda/Pipedream context, comparing version 2.33.0 with 2.32.2. Done means these commands recognize the existing .slack/hooks.json and work in CI without invalid_app_directory.

Written by the indexing model from the issue text.

Description

bug

The deno-slack versions

"deno-slack-sdk/": "https://deno.land/x/deno_slack_sdk@2.15.0/",
"deno-slack-api/": "https://deno.land/x/deno_slack_api@2.8.0/",

Deno runtime version

deno 2.2.2 (stable, release, x86_64-unknown-linux-gnu)
v8 13.4.114.9-rusty
typescript 5.7.3

OS info

We are running on AWS Lambda, specifically in Pipedream.

sw_vers: command not found
uname -v: #1 SMP Wed Jan 22 02:58:04 UTC 2025

Describe the bug

We always get this error, even though the file clearly exists:

This is an invalid Slack app project directory (invalid_app_directory)

Suggestion
   A valid Slack project includes the Slack hooks file: .slack/hooks.json

Steps to reproduce

slack activity -w something -a deployed --skip-update --no-color --token $SLACK_DATABOT_TOKEN

Or slack datastore bulk-put '{"datastore": "something"}' --from-file data.jsonl --app deployed --skip-update --token $SLACK_DATABOT_TOKEN

And probably other commands as well.

Expected result

It works, just as it did in version 2.32.2 and before.

Actual result

It doesn't work ("invalid Slack app"). See above.

Dominant language
Go
Stars
305
Forks
46
Avg merge
1d 11h
Merged PRs (30d)
23

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 slackapi/slack-cli

All issues in slackapi/slack-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.