Releases: pedroslopez/whatsapp-web.js
v1.16.5
This release brings important fixes for proper compatiblity with WhatsApp Web v2.2210.9.
Change log
3a2acf7 - chore: mark version v1.16.5
f32f3c7 - fix: get groupnotification chat
017dd4b - Update supported WhatsApp Web version to v2.2210.9 (#1340)
fa9f661 - fix(typings): Add ConnectOptions typings (#1354)
e9104b3 - Fix: Cannot read properties of undefined (reading 'getProfilePicFull') (#1362)
a23c285 - fix: group chat create (#1319)
281aec4 - Update supported WhatsApp Web version to v2.2208.7 (#1287)
v1.16.4
v1.16.3
Change log
24f8b46 - chore: mark version v1.16.3
9ab9c48 - fix(typings): LegacySessionAuth restartOnAuthFail
b966073 - getProfilePicture Fix => Evaluation failed: Error: Comms::sendIq called before startComms (#1264)
ea2cc81 - add feature request form template
56644f4 - add github ISSUE_TEMPLATE files (#1195)
v1.16.2
Change log
fcb78a1 - chore: mark version v1.16.2
f88bd27 - fix(LocalAuth): logout method (#1267)
c45fae5 - Fix get order. (#1274)
1b75d0d - fix(LocalAuth): only throw user-supplied userDataDir error if path is different
cc78e98 - add typings for LocalAuth attributes (#1262)
fc205ff - fix: Cannot destructure property 'session' of 'undefined' as it is undefined. (#1259)
v1.16.1
v1.16.0 - Multi Device Support
This release brings support for multidevice-enabled accounts to whatsapp-web.js. Thank you to everyone that contributed to the multidevice branch for making this possible. This release also brings a new way of handling authentication / session restoring.
Auth Strategies
To bring support for multidevice, we had to rethink how the library handles authentication due to internal changes in WhatsApp Web for how tokens are handled on MD.
To make changing how authentication works easier going forward and allow for more extensibility, 1.16 introduces the concept of Authentication Strategies. For more information on the available auth strategies and how they work, please check out the Guide.
Because of this change, the old way of passing session as a client option is now deprecated. But don't worry, you can keep using it via the LegacySessionAuth strategy until WhatsApp eventually removes non-md support.
We recommend everyone move to the LocalAuth strategy if possible, since it supports both MD and Non-MD accounts. We are aware that this method of authentication is less flexible and more difficult to move around, but we are working on ways of making this easier in the future.
Deprecations
These features are still available on 1.16, but will be removed in a later release.
session and restartOnAuthFail client options
As mentioned in the previous section, we are moving towards using auth strategies so these options have been deprecated. You should instead set them as options on the LegacySessionAuth strategy:
const authStrategy = new LegacySessionAuth({
session: {},
restartOnAuthFail: false
})
const client = new Client({ authStrategy })Phone-related properties and events
Because they are not available on MultiDevice and will be removed by WhatsApp in the future, properties and events that access information about the connected phone have been deprecated. This includes the battery events and client.info.phone.
Change log
979e97e - chore: mark version v1.16.0
1f4328c - fix tests
6691d25 - fix: message.getInfo() works for both MD and non-MD
12d9735 - Update README.md
ab5167c - fix: ChangeParticipantsPermissions typo in index.d.ts (#1206)
52c8336 - Added message duration in seconds (#1230)
9fe9169 - update tests to work with authStrategies
f6de161 - Auth Strategies (#1257)
0d55d40 - feat: Multi-device support (#889)
v1.15.8
v1.15.7
v1.15.6
v1.15.5
Change log
70ca073 - fix: send messages properly when disappearing mode is on (#1174)
7e36cce - extra options can override other options when sending message (#1103)
303ea3a - fix types and docs for Buttons class (#1070)
4aae8b0 - fix: sort before splicing when fetching messages
64803c2 - update typings for fetchMessages changes
aa9e19a - fetchMessages gets currently available messages by default (#1015)
7631400 - add back the pull_request trigger on lint
d7478de - fix: emit message events after ciphertext is decrypted
a9b2a1a - remove duplicated message type
3b46322 - fix: add missing message types
2200390 - disable eslint warning on intentionally skipped test
b1f7ff0 - chore(deps-dev): bump sinon from 12.0.1 to 13.0.1 (#1160)
21d5651 - chore(deps-dev): bump dotenv from 10.0.0 to 16.0.0 (#1171)
09cbee0 - chore(deps-dev): bump eslint-plugin-mocha from 9.0.0 to 10.0.3 (#1087)
fa9f5ab - Update supported WhatsApp Web version to v2.2202.12 (#1152)
c859ac3 - fix: dont crash when calling .destroy() while waiting for qr scan (#1172)
221d297 - remove unnecessary pull_request trigger for lint
078933f - fix(typings): add MessageTypes BUTTONS_RESPONSE (#1032)
f149516 - chore(tests): add Chat model tests (#784)
2f1c894 - add tests for takeoverOnConflict (#1170)
32e47d8 - fix: only emit disconnected event on navigation when state is PAIRING (#1169)
20aee44 - fix getLabels error (#1049)
bb2ef88 - fix: message.delete() can revoke for everyone (#1107)
6878598 - fix: await promise when setting user agent (#1113)