docs: update spectrum-ts documentation for v9.2.0#113
Closed
photon-action-bot[bot] wants to merge 1 commit into
Closed
docs: update spectrum-ts documentation for v9.2.0#113photon-action-bot[bot] wants to merge 1 commit into
photon-action-bot[bot] wants to merge 1 commit into
Conversation
|
Bugbot is not enabled for this team, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Contributor
|
Superseded by #114 which targets a newer version. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation Update: spectrum-ts v9.2.0
This PR updates documentation for spectrum-ts based on the v9.2.0 release.
Release Notes
New Features
Spectrum can now read
SPECTRUM_PROJECT_ID,SPECTRUM_PROJECT_SECRET, andSPECTRUM_WEBHOOK_SECRETautomatically when you leave those options out. Explicit config still wins.Provider string config fields can now come from env vars using
SPECTRUM_<PLATFORM>_<FIELD>. For example, Telegram readsSPECTRUM_TELEGRAM_BOT_TOKEN, and WhatsApp Business readsSPECTRUM_WHATSAPP_BUSINESS_PHONE_NUMBER_ID.WhatsApp Business can now boot direct mode from env vars when
accessTokenandphoneNumberIdare both set. Slack also supportsSPECTRUM_SLACK_ENDPOINT, while token maps still stay in code.Bug Fixes
Empty-string credential env vars are now treated as unset, so blank CI variables no longer break config parsing.
The platform-name env-var formatter no longer uses the regex pattern that triggered a CodeQL ReDoS warning.
Improvement
Version: 9.2.0
Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.