Bump version to 2.3.6 (#1354)

Author: sfc-gh-rsavenok

.cursor/skills/changelog-cleanup/SKILL.md

@@ -2,71 +2,122 @@
 name: changelog-cleanup
 description: >-
   Analyze and clean up the Upcoming Release section in CHANGELOG.md. Reviews
-  each entry for grammar and logic issues, then sorts entries into categories.
-  Use when the user mentions changelog cleanup, changelog sorting, release
-  notes review, or preparing a release.
+  each entry for grammar and logic issues, then sorts entries into named
+  sections. Use when the user mentions changelog cleanup, changelog sorting,
+  release notes review, or preparing a release.
 ---
 
 # Changelog Cleanup
 
 Cleans up the `## Upcoming Release` section of `CHANGELOG.md` in two phases:
-grammar/logic review, then sorting by category.
+grammar/logic review, then sorting into named sections.
+
+## Changelog structure
+
+Each release is a `## ` heading (e.g., `## Upcoming Release`, `## 2.3.6`).
+Within a release, entries are organized under **named sections** — plain-text
+labels followed by a colon, each followed by a blank line and then bullet
+entries. Section names are **not fixed**; they vary between releases. Common
+examples include `New features:`, `Changes:`, `Bugfixes:`, but there may be
+others (e.g., `Deprecations:`, `Breaking changes:`, `Performance:`).
+
+Example structure:
+
+```markdown
+## 2.3.6
+
+New features:
+
+- Entry one
+
+Changes:
+
+- Entry two
+
+Bugfixes:
+
+- Entry three
+- Entry four
+```
+
+Older releases (before 2.3.6) use a legacy flat list of bullets with no named
+sections. That format is no longer valid for new releases.
 
 ## Phase 1: Grammar and Logic Review
 
-1. Read `CHANGELOG.md` and extract all entries under `## Upcoming Release`
+1. Read `CHANGELOG.md` and extract all content under `## Upcoming Release`
    (stop at the next `## ` heading).
 2. For each entry, check for:
    - Spelling and grammar mistakes
    - Unclear or ambiguous phrasing
    - Logical issues (e.g., an entry starting with "Fixed" that actually
      describes a new feature, or contradictory statements)
+   - Entries placed under the wrong section (e.g., a bug fix listed under
+     "New features:")
 3. When an issue is found, use the `AskQuestion` tool to present the proposed
    fix to the user. Provide two options: "Accept" and "Reject".
    Batch related fixes into a single `AskQuestion` call when possible to
    reduce round-trips, but keep each fix clearly labeled.
 4. Apply only accepted fixes. Do not modify entries the user rejects.
 
-## Phase 2: Sort Entries
+## Phase 2: Sort Entries into Sections
 
-After grammar/logic fixes are applied, sort entries into four groups.
-Keep this exact order (no blank lines between groups):
+After grammar/logic fixes are applied, sort entries into named sections.
+Use these four sections in this exact order:
 
-### Group 1 — New features and additions
+### Section 1 — `New features:`
 
 Entries that semantically describe something new (e.g. `Added`), regardless of
 the leading verb.
 
-### Group 2 — Improvements and changes
+### Section 2 — `Changes:`
 
-Entries that describe enhancing, changing, or updating existing behavior
-(e.g. `Improved`, `Changed`, `Updated`), regardless of the leading verb.
+Entries that describe enhancing, changing, updating, removing, bumping
+dependencies, refactoring, or modifying existing behavior
+(e.g. `Improved`, `Changed`, `Updated`, `Removed`, `Bumped`, `Replaced`),
+regardless of the leading verb.
 
-### Group 3 — Bug fixes
+### Section 3 — `Bugfixes:`
 
 Entries that semantically describe fixing incorrect behavior (e.g. `Fixed`),
 regardless of the leading verb.
 
-### Group 4 — Other changes
+### Section 4 — Other (custom name)
 
-Everything else: dependency bumps, refactors, removals, tooling.
+If there are entries that don't fit the three sections above, use the
+`AskQuestion` tool to ask the user what section name to use for them, or
+whether to fold them into one of the existing sections.
 
 ### Sorting rules
 
 - Use the first word after `- ` as a signal, but override when the meaning
-  clearly fits a different group.
+  clearly fits a different section.
 - Multi-line entries (parent + indented sub-bullets) stay as one unit.
-- Preserve original relative order within each group.
-- No blank lines between groups.
+- Preserve original relative order within each section.
+- Omit sections that have no entries (don't output an empty section heading).
+- Each section heading is followed by a blank line, then its bullet entries.
+- Separate sections from each other with a blank line after the last bullet.
+
+## Output format
 
-## Example
+The final output under `## Upcoming Release` must look like:
 
 ```markdown
+## Upcoming Release
+
+New features:
+
 - Added support for OAuth tokens
 - Added new `timeout` option
+
+Changes:
+
 - Improved error details when OAuth fails
 - Changed default `jsonColumnVariantParser` to `JSON.parse`
+- Bumped axios to 1.14.0
+
+Bugfixes:
+
 - Fixed a crash when loading config
 - Fixed typo in error message
-- Bumped axios to 1.14.0
 ```

package.json

@@ -1,6 +1,6 @@
 {
   "name": "snowflake-sdk",
-  "version": "2.3.5",
+  "version": "2.3.6",
   "description": "Node.js driver for Snowflake",
   "engines": {
     "node": ">=18"