v2.0.6

What's Changed

• Fixes #256 with Thread-Aware Message Retrieval by @Joezanini in #266
• updating ci to fix build issue by @Joezanini in #271
• Revert "Fixes #256 with Thread-Aware Message Retrieval" by @Joezanini in #270
• Update containers.py by @guitarguy74 in #267
• Update room model by @ghpranav in #268
• Enhance room update functionality in tests by @Joezanini in #272

New Contributors

• @ghpranav made their first contribution in #268

Full Changelog: v2.0.5...v2.0.6

Docs, Tests, Bug fixes

v2.0.5 - Docs, Tests, Bug fixes

What's Fixed

• Fixed critical bug where malformed Retry-After headers from Webex API caused application crashes
• Applications now handle rate limit responses gracefully, even with unexpected header values
• Added comprehensive error handling for malformed API responses
• max parameter in the list_messages() function
• Contributor docs updated to reflect better local testing instructions

Impact

• Eliminates unexpected crashes during rate limit situations
• Improves application stability and user experience
• Maintains backward compatibility
• Always preserve critical parameters: Parameters like max, roomId, parentId, mentionedPeople, before, and beforeMessage are always preserved with their original values
• Consistent pagination: Ensures the max parameter maintains consistent page sizes across all pagination requests

Technical Details

• Enhanced RateLimitError constructor with robust error handling
• Added graceful fallback to 15-second retry intervals for malformed headers
• Comprehensive test coverage to prevent future regressions
• list_messages(roomId="123", max=10) will consistently return pages of 10 messages
• list_rooms(max=5) will consistently return pages of 5 rooms
• All other list methods will maintain consistent page sizes

v2.0.4

What's Changed

• fix(utils): only verify netloc if scheme isn't data by @adamweeks in #250

Full Changelog: v2.0.3...v2.0.4

v2.0.3

Remove backslash from f-string (Patch for Issue: #247) (#248)

Remove backslash from f-string to maintain backward compatibility with
Python 3.10 and 3.11 versions.

Also, corrected little (very minor non-impacting) cosmetic issues.

Patch for Issue: #247

v2.0.2

Webex Python SDK Release

We are excited to announce the latest release of the Webex Python SDK, which includes several enhancements and updates to improve functionality and compatibility. Below are the key changes introduced in this release:

Enhancements to Room Class and Rooms API

Additional Properties: The Room class has been enhanced with new properties to provide more detailed information and capabilities. These properties include:

• classificationId
• isAnnouncementOnly
• isReadOnly
• isPublic
• madePublic
• description

API Argument Fix: Corrected missing arguments in the rooms API to ensure proper functionality. This includes adding the necessary create room arguments to the post_data method.

Migration to Adaptive Card Version 1.3

Version Upgrade: The SDK has been upgraded from Adaptive Card 1.1 to 1.3. This includes a restructuring of code files to align with Adaptive Card's official documentation, ensuring compatibility and taking advantage of the latest features.

For more detailed information, please refer to the official Adaptive Cards documentation.
We encourage you to update to this latest version to benefit from these improvements. As always, your feedback is invaluable to us. Thank you for using the Webex Python SDK!

WebexPythonSDK 2.0 Documentation

Documentation for the newly named package webexpythonsdk is now hosted on github pages at https://webexcommunity.github.io/WebexPythonSDK/

What's Changed

• chore(docs): use rtd theme by @adamweeks in #238
• docs: update to gh-pages links by @adamweeks in #239

Full Changelog: v2.0.0...v2.0.1

webexpythonsdk v2.0.0 Now Released!

Welcome to the new webexpythonsdk library! The latest release removes support for Python v2 and is compatible with Python v3.10+. The new Webex Python SDK replaces the previous webexteamssdk; and with the exception of the Python version support and the name change, the two libraries are functionally equivalent. The new library is the recommended choice for new projects, and webexteamssdk users are encouraged to migrate.

Hotfix

This release is a hotfix that merges Pull request #175 into the main branch.

What's Changed

• Fix for #147 by @fbradyirl in #157
• Bump pygments from 2.6.1 to 2.7.4 by @dependabot in #158
• Fix type check in update by @mallamanis in #150
• Added option to disable ssl cert verification by @sQu4rks in #142
• Update Cards Handling to check correct attribute for instance of AdaptiveCards (solves #140) by @sQu4rks in #141
• fixing OpenUrl action by @craigers521 in #175

New Contributors

• @fbradyirl made their first contribution in #157
• @dependabot made their first contribution in #158
• @mallamanis made their first contribution in #150
• @craigers521 made their first contribution in #175

Full Changelog: v1.6...v1.6.1

The Catch-Up Release

In v1.6, we have updated all of the currently wrapped and supported Webex Teams API endpoints and closed out all existing issues that users opened on the v1.x releases. The library should now be up-to-date in supporting the Webex Teams APIs documented at developer.webex.com. It is not yet up-to-date in supporting the newer and broader Webex Meetings, Calling, and Devices APIs. We are tracking adding these additional API endpoints in issue #113, and we will work to add full support for all of the published Webex APIs in v2.x of the library.

With release v1.6, we are wrapping up active development on the v1.x release and shifting our focus to the next major release v2!

Breaking Change(s)

We have introduced one (1) breaking change in v1.6:

• We have changed the function signature (parameter names) for the WebexTeamsAPI.guest_issuer.create() method to align it with the developer documentation at developer.webex.com.

  Previous method definition:

  def create(self, subject, displayName, issuerToken, expiration, secret):
      ...

  def create(self, sub, name, iss, exp, secret):
      ...

Accessible Webex Tracking IDs & Custom User-Agent Header

Version 1.5 adds several minor backend improvements, including:

• Webex Tracking IDs are now prominently displayed for all API errors and warnings.

  Example Error Message:

  ApiError: [401] Unauthorized - The request requires a valid access token set in the Authorization request header. [Tracking ID: ROUTER_5F05F384-D9E9-01BB-00FF-4B0C804F00FF]
  

  You can also access the Tracking IDs via the tracking_id attribute available on the raised exception and warning objects.

  api = webexteamssdk.WebexTeamsAPI(access_token="abc")
  
  try:
      api.people.me()
  except webexteamssdk.ApiError as e:
      print(e.tracking_id)

• The webexteamssdk library now sends a custom User-Agent header (inspired by PIP's User-Agent header).

  Example User-Agent Header:

  webexteamssdk/1.5 {"implementation": {"name": "CPython", "version": "3.7.8"}, "distro": {"name": "macOS", "version": "10.15.5"}, "system": {"name": "Darwin", "release": "19.5.0"}, "cpu": "x86_64"}
  

• Minor package and PEP8 improvements.