Skip to content

chore(experiment): remove defaulted bolt and bolt-install experiments#363

Open
zimeg wants to merge 1 commit intomainfrom
bolt
Open

chore(experiment): remove defaulted bolt and bolt-install experiments#363
zimeg wants to merge 1 commit intomainfrom
bolt

Conversation

@zimeg
Copy link
Member

@zimeg zimeg commented Mar 4, 2026

Changelog

We concluded the bolt and bolt-install experiments with current and ongoing support of app development with the Bolt for JavaScript and Bolt for Python frameworks. This has been a default experience since v3.0.0 but now it's not noted as experimental.

Summary

This PR removes the defaulted bolt and bolt-install experiments as complete with ongoing support 🏁 ✨

Reviewers

Earlier logic to default the create and deploy and app selection branches of these experiments were removed in #141 and #158 and #162 so we might test the following for confidence:

$ slack create asdf  # Select a Bolt for Javascript or Bolt for Python app
$ cd asdf
$ slack run          # Create a new app from the included manifest file
$ rm manifest.json
$ slack run          # Confirm the remote manifest continues to be used
$ slack delete

No change for ROSI apps with the same commands 🥀

Notes

Ongoing iteration is still hoped in possibilities toward Bolt frameworks but I hope removing the experimental branches of install lets us focus to upcoming experiments with a perhaps timebound ⏳

Requirements

@zimeg zimeg added this to the Next Release milestone Mar 4, 2026
@zimeg zimeg self-assigned this Mar 4, 2026
@zimeg zimeg requested review from a team as code owners March 4, 2026 06:41
@zimeg zimeg added changelog Use on updates to be included in the release notes code health M-T: Test improvements and anything that improves code health experiment Experimental feature accessed behind the --experiment flag or toggle semver:patch Use on pull requests to describe the release version increment area:bolt-js Related to github.com/slackapi/bolt-js area:bolt-python Related to github.com/slackapi/bolt-python labels Mar 4, 2026
@codecov
Copy link

codecov bot commented Mar 4, 2026

Codecov Report

❌ Patch coverage is 76.47059% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 65.07%. Comparing base (c449532) to head (2b70a6c).

Files with missing lines Patch % Lines
internal/pkg/apps/install.go 69.23% 2 Missing and 2 partials ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #363   +/-   ##
=======================================
  Coverage   65.06%   65.07%           
=======================================
  Files         215      215           
  Lines       18179    18149   -30     
=======================================
- Hits        11829    11811   -18     
+ Misses       5254     5247    -7     
+ Partials     1096     1091    -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@srtaalej srtaalej left a comment

Choose a reason for hiding this comment

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

big thanks for updating this! yay to cleaner code 🚀 💟

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:bolt-js Related to github.com/slackapi/bolt-js area:bolt-python Related to github.com/slackapi/bolt-python changelog Use on updates to be included in the release notes code health M-T: Test improvements and anything that improves code health experiment Experimental feature accessed behind the --experiment flag or toggle semver:patch Use on pull requests to describe the release version increment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants