Skip to content

fix: print the Business tier with its name in the startup log - #45

Merged
Musiker15 merged 1 commit into
mainfrom
fix/business-tier-label
Nov 5, 2026
Merged

Musiker15 merged 1 commit into
mainfrom
fix/business-tier-label

Conversation

@Musiker15

Copy link
Copy Markdown
Member

Description

TIER_LABELS in src/client.js had no entry for business, so a bot on the Business tier printed the raw key on startup: API key valid → business. It prints Business now. Seen on the MSK support bot after the 2.22.0 update. The colour falls back to the default green as before.

No release with this one, it goes out with the next version.

Related Issue

None.

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (fix or feature that changes existing behavior)
  • 🌍 Translation / locale update
  • 📖 Documentation only
  • 🔧 Refactor / chore (no functional change)

How Was This Tested?

npm test: 391 passed. One-line change to a console label.

Checklist

  • My code follows the project's conventions
  • No new production dependencies were added
  • User-facing strings go through client.t(...) (not applicable, console log label)
  • Any DB schema change uses an inline migration (no schema change)
  • The bot still works without MSK_API_KEY
  • The bot starts cleanly (npm start) and I verified my change on a test server
  • I updated the relevant docs (none affected)
  • I added a CHANGELOG.md entry under [Unreleased]
  • My commit messages are in English and follow Conventional Commits

@Musiker15
Musiker15 merged commit 501090f into main Nov 5, 2026
6 checks passed
@Musiker15
Musiker15 deleted the fix/business-tier-label branch November 5, 2026 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant