Bump to v1.8.5

Author: jdalton

CHANGELOG.md

@@ -4,6 +4,14 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
+## [1.8.5](https://github.com/SocketDev/socket-sdk-js/releases/tag/v1.8.5) - 2025-10-02
+
+### Changed
+- Synced with OpenAPI definition
+  - Added new `/openapi.json` endpoint for retrieving API specification in JSON format
+  - Updated repo label filter descriptions to document empty string ("") usage for repositories with no labels
+  - Added 'dual' threat category type
+
 ## [1.8.4](https://github.com/SocketDev/socket-sdk-js/releases/tag/v1.8.4) - 2025-10-01
 
 ### Fixed

CLAUDE.md

@@ -187,6 +187,20 @@ All code elements MUST be sorted:
   - **Important**: Even when using `--no-verify`, you MUST still run linting/checking commands manually first
   - **Rationale**: Pre-commit hooks run linting and type-checking which are critical for SDK source code but less critical for non-published files
 
+### Changelog Management
+- **🚨 MANDATORY**: When creating changelog entries for version bumps:
+  - **Check OpenAPI definition updates**: Always analyze `types/api.d.ts` changes
+    ```bash
+    git diff v{previous-version}..HEAD -- types/
+    ```
+  - **Document user-facing changes**: Include specific details about:
+    - New endpoints added (e.g., `/openapi.json`)
+    - Updated parameter descriptions and behavior
+    - New type categories or enum values (e.g., 'dual' threat type)
+    - Breaking changes to API contracts
+  - **Focus on user impact**: Only include changes that affect SDK users, not internal infrastructure
+  - **Rationale**: OpenAPI changes directly impact SDK users and must be documented for API discoverability
+
 ## 🔍 DEBUGGING
 
 ### Common Issues

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@socketsecurity/sdk",
-  "version": "1.8.4",
+  "version": "1.8.5",
   "license": "MIT",
   "description": "SDK for the Socket API client",
   "author": {