Merge branch 'main' of https://github.com/slackapi/node-slack-sdk into feat-work-objects

Author: vegeris

.github/maintainers_guide.md

@@ -52,17 +52,17 @@ Releasing can feel intimidating at first, but rest assured: if you make a mistak
 
 4. For each package to be released, run `npm run test` to verify that tests are passing and code is free of linting errors.
 
-5. Generate the reference docs for that package by running `npm run docs`.
+5. On our new branch, bump the version(s) in `package.json` (see [Versioning and Tags](https://github.com/slackapi/node-slack-sdk/blob/main/.github/maintainers_guide.md#-versioning-and-tags))
 
-6. On your new branch, bump the version(s) in `package.json` (see [Versioning and Tags](https://github.com/slackapi/node-slack-sdk/blob/main/.github/maintainers_guide.md#-versioning-and-tags))
+    - Generate the reference docs for that package by running `npm run docs`.
 
     - Make a single commit for the version(s) bump, following the format in: ([Example](https://github.com/slackapi/node-slack-sdk/commit/1503609d79abf035e9e21bad7360e124e4211594))
 
     - Create a pull request for the version change ([Example](https://github.com/slackapi/node-slack-sdk/pull/1059))
 
     - Add appropriate labels on the PR, including `release`
 
-7. Once the PR has been approved and tests have passed, merge it into the main repository.
+6. Once the PR has been approved and tests have passed, merge it into the main repository.
 
     -  Check out your local `main` branch and update it to get the latest changes: `git checkout main && git pull origin main`
 
@@ -77,15 +77,15 @@ Releasing can feel intimidating at first, but rest assured: if you make a mistak
 
     - Run `npm publish . --otp YOUR_OTP_CODE`. To generate an OTP (One Time Password), use your password generator of choice (Duo, 1Password)
 
-9. Close GitHub Milestone(s)
+8. Close GitHub Milestone(s)
 
     - Close the relevant GitHub Milestone(s) for the release(s)
 
     - Check the existing GitHub Milestones to see if the next minor version exists. If it doesn't, then create a GitHub Milestone for new issues to live in. Typically, you'll create a new minor version - however, if there are any bugs that need to be carried over from the current GitHub Milestone, you could make a Milestone for a patch version to reflect those issues
 
     - Move any unfinished, open issues to the next GitHub Milestone
 
-10. Create GitHub Release(s) with release notes
+9. Create GitHub Release(s) with release notes
 
     - From the repository, navigate to the **Releases** section and draft a new release
 
@@ -97,7 +97,7 @@ Releasing can feel intimidating at first, but rest assured: if you make a mistak
 
     - Once the release notes are ready, click the "Publish Release" button to make them public
 
-11. Communicate the release (as appropriate)
+10. Communicate the release (as appropriate)
 
     - **Internal**
 
@@ -138,19 +138,19 @@ Releasing can feel intimidating at first, but rest assured: if you make a mistak
 
     -  Push the new tag up to origin: `git push --tags origin`
 
-5. Publish the release to npm
+6. Publish the release to npm
 
     - Run `npm publish --tag <dist-tag> . --otp YOUR_OTP_CODE`
 
       - `<dist-tag>` should be a label representative of the beta release. It could be feature-specific (i.e. `feat-token-rotation`) or it can be a generic release candidate (i.e. `2.5.0rc`). Whatever you decide: it must _not_ be `latest`, as that is reserved for non-beta releases.
 
     - To generate an OTP (One Time Password), use your password generator of choice (Duo, 1Password)
 
-6. Test that the publish was successful
+7. Test that the publish was successful
 
     - Run `npm info <PACKAGE_NAME> dist-tags`
 
-7. Create GitHub Release(s) with release notes
+8. Create GitHub Release(s) with release notes
 
     - From the repository, navigate to the **Releases** section and draft a new release
 
@@ -163,7 +163,7 @@ Releasing can feel intimidating at first, but rest assured: if you make a mistak
 ### 🔖 Versioning and Tags
 This project is versioned using [Semantic Versioning](http://semver.org/), particularly in the [npm flavor](https://docs.npmjs.com/getting-started/semantic-versioning). Each release is tagged using git. The naming convention for tags is `{package_name}@{version}`. For example, the tag `@slack/web-api@v5.0.0` marks the v5.0.0 release of the `@slack/web-api` package. A single commit will have multiple tags when multiple packages are released simultaneously.
 
-One package that expands upon the standard major.minor.patch version schema typically associated with Semantic Versioning is the `@slack/cli-test` package. This package employs standard major.minor.patch version, in addition to a [build metadata suffix](https://semver.org/#spec-item-10) suffix of the form `+cli.X.Y.Z`, e.g. `0.1.0+cli.2.24.0`. The version after `+cli.` communicates compatibility between the `@slack/cli-test` package and the [Slack CLI](https://docs.slack.dev/slack-cli/) itself.
+One package that expands upon the standard major.minor.patch version schema typically associated with Semantic Versioning is the `@slack/cli-test` package. This package employs standard major.minor.patch version, in addition to a [build metadata suffix](https://semver.org/#spec-item-10) suffix of the form `+cli.X.Y.Z`, e.g. `0.1.0+cli.2.24.0`. The version after `+cli.` communicates compatibility between the `@slack/cli-test` package and the [Slack CLI](https://docs.slack.dev/tools/slack-cli/) itself.
 
 ### 🪵 Branches
 `main` is where active development occurs. Long running named feature branches are occasionally created for collaboration on a feature that has a large scope (because everyone cannot push commits to another person's open Pull Request). After a major version increment, a maintenance branch for the older major version is left open (e.g. `v3`, `v4`, etc).

.github/workflows/ci-build.yml

@@ -33,7 +33,7 @@ jobs:
         run: |
           git config --global core.autocrlf false
           git config --global core.eol lf
-      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
         with:
           persist-credentials: false
       - name: Use Node.js ${{ matrix.node-version }}
@@ -90,7 +90,7 @@ jobs:
           files: packages/${{ matrix.package }}/coverage/lcov.info
       - name: Upload code coverage
         if: matrix.node-version == '22.x' && matrix.os == 'ubuntu-latest' && steps.check_coverage.outputs.files_exists == 'true'
-        uses: codecov/codecov-action@18283e04ce6e62d37312384ff67231eb8fd56d24 # v5.4.3
+        uses: codecov/codecov-action@fdcc8476540edceab3de004e990f80d881c6cc00 # v5.5.0
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
           directory: packages/${{ matrix.package }}/coverage

docs/english/reference/cli-test/index.md

@@ -1,4 +1,4 @@
-# @slack/cli-test v2.1.0+cli.2.32.2
+# @slack/cli-test v2.2.0+cli.2.32.2
 
 ## Classes
 

docs/english/reference/cli-test/variables/SlackCLI.md

@@ -6,7 +6,7 @@
 const SlackCLI: object;
 ```
 
-Defined in: [cli/index.ts:21](https://github.com/slackapi/node-slack-sdk/blob/main/packages/cli-test/src/cli/index.ts#L21)
+Defined in: [cli/index.ts:22](https://github.com/slackapi/node-slack-sdk/blob/main/packages/cli-test/src/cli/index.ts#L22)
 
 Set of functions to spawn and interact with Slack Platform CLI processes and commands
 
@@ -815,3 +815,23 @@ update: (args) => Promise<string>;
 `Promise`\<`string`\>
 
 command output
+
+### version
+
+```ts
+version: object;
+```
+
+#### version.version()
+
+```ts
+version: () => Promise<string>;
+```
+
+`slack version`
+
+##### Returns
+
+`Promise`\<`string`\>
+
+command output

docs/english/reference/oauth/index.md

@@ -1,4 +1,4 @@
-# @slack/oauth v3.0.3
+# @slack/oauth v3.0.4
 
 ## Enumerations
 

docs/english/reference/rtm-api/index.md

@@ -1,4 +1,4 @@
-# @slack/rtm-api v7.0.3
+# @slack/rtm-api v7.0.4
 
 ## Enumerations
 

docs/english/reference/socket-mode/index.md

@@ -1,4 +1,4 @@
-# @slack/socket-mode v2.0.4
+# @slack/socket-mode v2.0.5
 
 ## Enumerations
 

examples/openid-connect/package.json

@@ -10,7 +10,7 @@
   "license": "MIT",
   "repository": "slackapi/node-slack-sdk",
   "dependencies": {
-    "@koa/router": "^13.0.0",
+    "@koa/router": "^14.0.0",
     "@slack/web-api": "^7.3.4",
     "jsonwebtoken": "^9.0.2",
     "koa": "^3.0.0",

packages/cli-test/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@slack/cli-test",
-  "version": "2.1.0+cli.2.32.2",
+  "version": "2.2.0+cli.2.32.2",
   "description": "Node.js bindings for the Slack CLI for use in automated testing",
   "author": "Salesforce, Inc.",
   "license": "MIT",

packages/cli-test/src/cli/commands/version.spec.ts

@@ -0,0 +1,32 @@
+import sinon from 'sinon';
+
+import { mockProcess } from '../../utils/test';
+import { shell } from '../shell';
+import version from './version';
+
+describe('version commands', () => {
+  const sandbox = sinon.createSandbox();
+  let spawnSpy: sinon.SinonStub;
+
+  beforeEach(() => {
+    const process = mockProcess();
+    spawnSpy = sandbox.stub(shell, 'spawnProcess').returns({
+      command: 'version',
+      finished: true,
+      output: 'Using slack v3.4.5',
+      process,
+    });
+    sandbox.stub(shell, 'checkIfFinished').resolves();
+  });
+  afterEach(() => {
+    sandbox.restore();
+  });
+
+  describe('version method', () => {
+    it('should invoke `version`', async () => {
+      const actual = await version.version();
+      sandbox.assert.calledWith(spawnSpy, sinon.match.string, sinon.match.array.contains(['version']));
+      sinon.assert.match(actual, 'v3.4.5');
+    });
+  });
+});