chore: release v4.8.6

Author: zeative

.changeset/baileys-rc14.md

@@ -1,5 +1,32 @@
 # zaileys
 
+## 4.8.6
+
+### Patch Changes
+
+- dd9edb4: Upgrade baileys to 7.0.0-rc14 (pulls patched `ws` 8.21.0, newer WhatsApp Web version, and a profile-picture tc-token fix), bump `jimp` to `^1.6.1` to satisfy the new peer range, update `valibot` to `^1.4.2`, and pin `protobufjs` to `^7.6.5` via a pnpm override.
+- b3a552f: Add group status support. `client.send(groupJid).groupStatus(text, { backgroundColor, font })` posts a group status, and `groupStatus(message)` reposts an existing text message as one. Groups only: a non-`@g.us` recipient rejects with `INVALID_RECIPIENT`.
+
+  Verified against a live WhatsApp session: plain text, hex background, raw ARGB-integer background, a named font, reposting a text message, and overriding its text all render in an ordinary `@g.us` group, and a non-group recipient is rejected. `backgroundColor` accepts both a hex string and a raw ARGB integer — baileys' own `assertColor` silently returns `undefined` for numeric input, so zaileys parses colours itself. One caveat: `.mentions()` attaches `mentionedJid` but WhatsApp does not render a visible mention on a group status.
+
+  **Text only.** Reposting an image, video, or voice note rejects with `INVALID_OPTIONS`. Eight variants were relayed against a live session and none rendered, while that same session posted a media `status@broadcast` that did render — so the limitation is the group-status envelope, not the media pipeline, and text in the same envelope works. A status that silently vanishes is worse than a clear error, so it is blocked.
+
+  Two pre-existing bugs are fixed alongside it.
+
+  **Behaviour change — inbound group statuses now fire events.** `groupStatusMessage` and `groupStatusMessageV2` were missing from the decoder's wrapper list, so every inbound group status was silently dropped: no `message`, no `text`, no `image`. They now decode to their inner content, so `chatType` reflects what the status contains rather than the envelope. Handlers that route commands off `message`/`text` will start seeing group status posts. Use the new `ctx.isGroupStatus` flag to skip them:
+
+  ```typescript
+  client.on('message', (ctx) => {
+    if (ctx.isGroupStatus) return;
+  });
+  ```
+
+  `ctx.isGroupStatus` is distinct from the existing `ctx.isGroupStatusMention`, which means someone mentioned this group in _their_ status. This decode path is covered by unit fixtures; it has not been exercised against a real WhatsApp-generated group status, because the WhatsApp client used for testing offers no way to post one.
+
+  **Relay path now applies message modifiers.** `.mentions()`, `.mentionAll()`, and `.disappearing()` were silently dropped for every relay-based content type — `buttons`, `list`, `carousel`, `template`, `groupInvite`, and AIRich. They are now applied to the message, and relayed messages carry a `messageSecret` for parity with the normal send path.
+
+- f10106d: Add customizable sticker pack and author metadata via `ClientOptions.sticker` and per-message `.sticker(src, { pack, author })`, plus improved quoted-message context resolution in direct chats.
+
 ## 4.8.5
 
 ### Patch Changes

.changeset/group-status.md

@@ -1,7 +1,7 @@
 {
   "name": "zaileys",
   "description": "Zaileys - Simplified WhatsApp Node.js TypeScript/JavaScript API",
-  "version": "4.8.5",
+  "version": "4.8.6",
   "license": "MIT",
   "type": "module",
   "main": "./dist/index.cjs",