-
Notifications
You must be signed in to change notification settings - Fork 198
TeamsJS Releases
The goal is that official releases happen monthly on the first Wednesday of each month.
Beta versions are published weekly on all Wednesdays where there is not an official release. Beta releases are similar to official releases except:
The TeamsJS package can be consumed either via npm in your build process or via a <script>
tag reference to the CDN at runtime.
Official releases and beta releases are both published to the npm feed. However, only an official release is ever marked "latest" on npm. Beta builds are always available via npm , but you have to manually reference them (you can see them on the versions tab.
Both official and beta releases are published to the CDN, but in different locations. Official releases always live at a URL like this:
https://res.cdn.office.net/teams-js/<VERSION NUMBER>/js/MicrosoftTeams.min.js
.
You can find the URL for a particular official version in the README
for that version (which is shown on the npm page for the version). E.g., for 2.18.0, the README
shows:
<script
src="https://res.cdn.office.net/teams-js/2.18.0/js/MicrosoftTeams.min.js"
integrity_no="sha384-g8DoRkiR0ECQ9rwKIgY8GjQ5h0d2jp1347CmU/IRlyUHPjJZiFWEOYc+hFtT9MGL"
crossorigin="anonymous"
></script>
Beta releases are only published to the sdf CDN endpoint, which has a slightly different URL:
https://res-sdf.cdn.office.net/teams-js/<BETA VERSION NUMBER>/js/MicrosoftTeams.min.js
For example, beta release 2.19.0-beta.1 is located here:
https://res-sdf.cdn.office.net/teams-js/2.19.0-beta.1/js/MicrosoftTeams.min.js
Since the README
is not updated for beta releases, you will have to hand-craft the CDN URL for them using the pattern shown above.