Key Changes

Manifest Management Shift Bolt JavaScript and Bolt Python projects now default to using the local manifest.json file as the source of truth for app configuration, replacing the previous behavior of pulling manifests from remote app settings. This change simplifies local development workflows and reduces confusion when manifest configurations diverge between local and cloud versions.

Improved Manifest Conflict Detection When changes are detected between your local manifest and app settings, the CLI now prompts you before taking action. The new warning clearly indicates that the app settings manifest will be overwritten by your project's local manifest, and alerts you to any changes in app settings that aren't reflected locally—helping prevent accidental loss of configuration.

Project Creation Enhancements The slack create command now automatically normalizes project directory names to kebab-case (e.g., "My App" → my-app), ensuring consistent naming conventions. The app name prompt also displays a randomly generated suggestion as placeholder text, making it easier to accept defaults or provide custom names.

Command Updates The slack app link command now fully supports projects using local manifest files, removing warning messages and preserving your current manifest source configuration. A helpful tip displays the location (.slack/config.json) where you can adjust manifest source settings.

Bug Fixes Python virtual environment activation failures now generate warnings instead of errors, allowing the CLI to continue operating gracefully when .venv/ activation encounters issues.

Action Items

• Check your .slack/config.json file to verify the "manifest.source": "local" setting after updating
• Review any app settings changes that may not be reflected in your local manifest.json
• Update any automation that relied on manifest source behavior