docs: Remove beta/alpha notices from stable features #1049
Conversation
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
Add comprehensive documentation for the Ultraloq smart lock integration, including the unique timezone configuration requirement for time-bound access codes. New documentation: - Ultraloq integration overview (README.md) - Setup guide with OAuth flow and timezone configuration - Detailed timezone configuration guide - Access code creation guide (permanent and time-bound codes) Updates: - Add Ultraloq to SUMMARY.md navigation (alphabetically between TTLock and Wyze) - Enhance /devices/report_provider_metadata API reference with Ultraloq use case and examples - Update access code constraints guide to include provider-specific timezone requirements The Ultraloq integration is unique in requiring manual timezone configuration before creating time-bound access codes, as Ultraloq devices schedule codes using device-local time without reporting their timezone. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Update the timezone requirement detection code sample to include examples in Python, JavaScript, Ruby, PHP, C#, Java, and cURL, consistent with other SDK code samples throughout the documentation.
Expand the Next Steps section with working code examples for: - Lock and unlock operations - Creating permanent access codes - Creating time-bound access codes - Monitoring device status (lock status, online/offline, battery) All examples include multi-language tabs (Python, JS, Ruby, PHP, C#, Java, cURL) to help developers quickly implement common operations after setup.
Add requirement that ALL code examples must include all supported Seam SDK languages (Python, JavaScript, Ruby, PHP, C#, Java) plus cURL for direct API access. Update the multi-language code example section with: - Explicit requirement to include all languages - Complete example showing all 7 languages - Standard language ordering - Guidance on when to include code examples This ensures consistency across all documentation and makes it easier for developers using different languages to find relevant examples.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Remove all "Early Access Preview", "currently in Alpha/Beta", and "breaking changes" notices from: - Access Grants API - Access Methods API - Spaces API - Customer Portals API - Reservation Automations These features are now stable and production-ready. Updated source data file (paths.yaml) and regenerated all API documentation. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Removes all beta/alpha/early access notices from features that are now stable and production-ready.
Motivation
Customer feedback indicated that beta/alpha notices for Access Grants, Customer Portals, and Automations were causing concern, even though these features are now stable and widely used in production.
Changes
Updated Features (no longer marked as alpha/beta):
Files Changed: 194 files
Source data (codegen/data/paths.yaml)
alphafields from/access_grants,/access_methods,/spaces, and/customersendpointsCapability guides (10 files)
API documentation (auto-regenerated)
npm run generateRemoved Notices
All instances of:
Testing
Impact
These features will now appear production-ready to customers, improving confidence in using them for production deployments.