Skip to content

Conversation

simplesagar
Copy link
Member

@simplesagar simplesagar commented Jul 17, 2025

Summary

  • Add support for OSS (Open Source Software) license type with Business tier privileges
  • Enable OSS projects to access premium features like SDK testing
  • Backward compatible implementation that doesn't break existing functionality

Changes Made

  • Added IsBusinessTierOrAbove() helper functions that recognize OSS accounts alongside Business/Enterprise
  • Updated CheckTestingEnabled() to use new helper for account type validation
  • Updated CheckTestingAccountType() to support OSS accounts
  • Added comprehensive unit tests to verify OSS account type functionality

Test Plan

  • Unit tests pass for all account types (Free, Business, Enterprise, OSS)
  • OSS accounts now have same testing privileges as Business accounts
  • Existing account types continue to work as before
  • Code compiles without syntax errors

Technical Details

Since the external SDK (speakeasy-client-sdk-go) doesn't include "OSS" as an account type enum, the implementation uses string comparison to detect OSS accounts and treats them identically to Business accounts for all feature checks.

🤖 Generated with Claude Code

https://linear.app/speakeasy/issue/DOCS-4760/feature-add-license-type-oss

Add support for OSS (Open Source Software) license type that has the same
feature access as Business tier accounts. This enables OSS projects to
access premium features like SDK testing.

Changes:
- Add IsBusinessTierOrAbove() helper functions that recognize OSS accounts
- Update CheckTestingEnabled() to use new helper for account type validation
- OSS accounts now have same testing privileges as Business/Enterprise tiers
- Add comprehensive tests to verify OSS account type functionality

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
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