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

[mroy-seedbox]

The deno-slack versions

"deno-slack-sdk/": "https://deno.land/x/[email protected]/",
"deno-slack-api/": "https://deno.land/x/[email protected]/",

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.

[mroy-seedbox]

The issue initially appeared in version 2.33.0.

Unfortunately, version 3.0.0 did not resolve the issue. 😞

Related:

• [BUG] Workflow app deployment via CI is not working. #437

[mroy-seedbox]

Output from slack doctor:

SYSTEM

    ✔ Operating System (the computer conductor)
        Version: linux (amd64)

    ✔ Git (a version control system)
        Version: git version 2.40.1


SLACK

    ✔ CLI (this tool for building Slack apps)
        Version: v3.0.0

    ✔ Configurations (any adjustments to settings)
        System ID: 31ec8d9e-b4c1-4958-9a80-065fcdb2f3f4
        Last updated: 0001-01-01 00:00:00 Z
        Experiments: bolt

    ✘ Credentials (your Slack authentication)
      Error: You are either not logged in or your login session has expired (not_authed)
      Suggestion: Authorize your CLI with `slack login`

Errors: 1

No credentials (as expected) since this is a CI context (so using --token instead).

[mwbrooks]

Hey @mroy-seedbox 👋🏻 I'm deeply sorry that your deployment setup is affected by this bug 😢 But thank you for including so much detail!

We'll look into reproducing your problem and double-checking the other commands with the --token flag. We'll aim to have a fix available in the next release and I can loop around on this issue when it's available.

Without the Slack CLI being open sourced, it's been challenging to get the rich feedback that you provided in this issue. While we have unit test coverage and a E2E test pipeline, these issues can still slip through - unfortunately. On the upside, we've got the go-ahead to open source the Slack CLI, so hopefully we can provide more detailed release information and a dedicated issue tracker for feedback.

[mroy-seedbox]

Oh, I would've definitely submitted a PR if it were open source!! Can't wait! 😄 🙌 🚀

And thanks for the response. 🙏

In the meantime, we're pinned on 2.32.2, so not the end of the world.