- Ably FAQs
- Realtime API and client libraries
- Common issues
-
Account billing and packages
-
General
-
Realtime API and client libraries
-
Troubleshooting
-
Channels
-
REST API and client libraries
-
Ably error codes
-
Account and app setup and configuration
-
Ably architecture, transports, and security
-
Performance and Redundancy
-
Push Notifications
-
Integrations
-
Migrating to Ably from an existing service
Why am I seeing a deprecation warning when serving Javascript files from your CDN?
These non-versioned URLs however are no longer supported. The reason behind this is that if we need to release a breaking change in the Javascript library (like we did for our v1.0 release), we cannot do that safely without potentially breaking existing apps using the non-versioned Javascript file from our CDN.
So in order to ensure Ably can guarantee no breaking changes via our CDN, customers must now choose to lock into a specific major, minor or patch version according to the Semantic Versioning scheme.
For example:
- If you want to automatically get all minor release updates in version 1 of our client library, you can use http://cdn.ably.com/lib/ably.min-1.js. This will automatically use the latest 1.*.* version releases.
- If you want to lock into a specific minor version release, you can use http://cdn.ably.com/lib/ably.min-1.0.js. This will automatically use the latest 1.0.* version releases.
- If you want to lock into a patch release, you can use http://cdn.ably.com/lib/ably.min-1.0.0.js. This will automatically use only version 1.0.0 of the client library.