Skip to content

Conversation

@zimeg
Copy link
Member

@zimeg zimeg commented Feb 12, 2026

Summary

This PR updates the release notes for maintainers on testing and publishing steps for releases!

Requirements

@zimeg zimeg requested a review from srtaalej February 12, 2026 04:14
@zimeg zimeg self-assigned this Feb 12, 2026
@zimeg zimeg requested a review from a team as a code owner February 12, 2026 04:14
@zimeg zimeg added docs M-T: Documentation work only semver:patch release labels Feb 12, 2026
@changeset-bot
Copy link

changeset-bot bot commented Feb 12, 2026

⚠️ No Changeset found

Latest commit: c8af0f1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@codecov
Copy link

codecov bot commented Feb 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.17%. Comparing base (756d8b9) to head (c8af0f1).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2512   +/-   ##
=======================================
  Coverage   93.17%   93.17%           
=======================================
  Files          40       40           
  Lines       11384    11384           
  Branches      726      726           
=======================================
  Hits        10607    10607           
  Misses        765      765           
  Partials       12       12           
Flag Coverage Δ
cli-hooks 95.42% <ø> (ø)
cli-test 94.79% <ø> (ø)
oauth 77.39% <ø> (ø)
socket-mode 61.87% <ø> (ø)
web-api 98.12% <ø> (ø)
webhook 96.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Member Author

@zimeg zimeg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📬 Leaving a few notes for wonderful reviewers!

1. **Check GitHub Milestones**: Before merging the release PR please check the relevant [Milestones](https://github.com/slackapi/node-slack-sdk/milestones). If issues or pull requests are still open either decide to postpone the release or save those changes for a future update.

2. **Review the release PR**: Verify that version bumps match expectations, `CHANGELOG` entries are clear, and CI checks pass.
2. **Review the release PR**: Verify that version bumps match expectations, `CHANGELOG` entries are clear, and CI checks pass on the `main` branch.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🪵 note: Running tests on commits created from GitHub Actions IIRC requires additional scopes that only an app can access. We might follow up with a custom "release" bot but I'm uncertain if that's the best approach at the moment...

Here's a recent release for reference:

🔗 #2509

2. **Review the release PR**: Verify that version bumps match expectations, `CHANGELOG` entries are clear, and CI checks pass on the `main` branch.

3. **Merge and approve**: Merge the release PR, then approve the publish workflow to release packages to npm.
3. **Merge and approve**: Merge the release PR, then approve the [publish](https://github.com/slackapi/node-slack-sdk/actions/workflows/release.yml) workflow to release packages to npm.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔏 note: This is required lest a pending workflow remain pending! Now we link to the page for approval.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Super good call out!

@zimeg zimeg enabled auto-merge (squash) February 12, 2026 04:23
Copy link
Member

@mwbrooks mwbrooks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Thanks for keeping out docs updated. Really good call out to approve the workflow - that can be easily overlooked by folks new to the release process.

2. **Review the release PR**: Verify that version bumps match expectations, `CHANGELOG` entries are clear, and CI checks pass on the `main` branch.

3. **Merge and approve**: Merge the release PR, then approve the publish workflow to release packages to npm.
3. **Merge and approve**: Merge the release PR, then approve the [publish](https://github.com/slackapi/node-slack-sdk/actions/workflows/release.yml) workflow to release packages to npm.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Super good call out!

@zimeg zimeg merged commit a9fa6c1 into main Feb 12, 2026
58 checks passed
@zimeg zimeg deleted the zimeg-docs-releases-steps branch February 12, 2026 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs M-T: Documentation work only release semver:patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants