From 53d46e308abf24d50b8dc2f3c0521d13ff9735fa Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Sat, 15 Feb 2025 10:58:07 +0000
Subject: [PATCH] [CI] Release

---
 .changeset/little-coins-invent.md         | 28 -------------------
 .changeset/spicy-guests-draw.md           |  5 ----
 packages/annotation-comments/CHANGELOG.md | 33 +++++++++++++++++++++++
 packages/annotation-comments/package.json |  6 +++--
 4 files changed, 37 insertions(+), 35 deletions(-)
 delete mode 100644 .changeset/little-coins-invent.md
 delete mode 100644 .changeset/spicy-guests-draw.md

diff --git a/.changeset/little-coins-invent.md b/.changeset/little-coins-invent.md
deleted file mode 100644
index 81f3af8..0000000
--- a/.changeset/little-coins-invent.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-'annotation-comments': minor
----
-
-Adds support for target ranges defined by matching `start`...`end` annotation comments. This allows you to annotate ranges of code without having to count lines or manually updating the ranges when the code changes.
-
-The following example shows how to define a simple target line range using the new feature:
-
-```js
-// [!mark:start]
-function foo() {
-  console.log('foo')
-}
-// [!mark:end]
-```
-
-You can also combine `start`...`end` ranges with search queries, which limits the search to the range defined by the `start` and `end` annotation comments:
-
-```js
-// [!mark:"log":start]
-function foo() {
-  console.log('The words "log" will be marked both in the method call and this text.')
-  console.log('Also on this line.')
-}
-// [!mark:"log":end]
-
-console.log('As this line is outside the range, "log" will not be marked.')
-```
diff --git a/.changeset/spicy-guests-draw.md b/.changeset/spicy-guests-draw.md
deleted file mode 100644
index 90e767a..0000000
--- a/.changeset/spicy-guests-draw.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'annotation-comments': major
----
-
-First major release. Mainly to ensure that semver ranges work as expected, but hooray! 🎉
diff --git a/packages/annotation-comments/CHANGELOG.md b/packages/annotation-comments/CHANGELOG.md
index 2ef8994..c7b10d8 100644
--- a/packages/annotation-comments/CHANGELOG.md
+++ b/packages/annotation-comments/CHANGELOG.md
@@ -1,5 +1,38 @@
 # annotation-comments
 
+## 1.0.0
+
+### Major Changes
+
+- a5b2179: First major release. Mainly to ensure that semver ranges work as expected, but hooray! 🎉
+
+### Minor Changes
+
+- a5b2179: Adds support for target ranges defined by matching `start`...`end` annotation comments. This allows you to annotate ranges of code without having to count lines or manually updating the ranges when the code changes.
+
+  The following example shows how to define a simple target line range using the new feature:
+
+  ```js
+  // [!mark:start]
+  function foo() {
+    console.log('foo')
+  }
+  // [!mark:end]
+  ```
+
+  You can also combine `start`...`end` ranges with search queries, which limits the search to the range defined by the `start` and `end` annotation comments:
+
+  ```js
+  // [!mark:"log":start]
+  function foo() {
+    console.log('The words "log" will be marked both in the method call and this text.')
+    console.log('Also on this line.')
+  }
+  // [!mark:"log":end]
+
+  console.log('As this line is outside the range, "log" will not be marked.')
+  ```
+
 ## 0.3.0
 
 ### Minor Changes
diff --git a/packages/annotation-comments/package.json b/packages/annotation-comments/package.json
index 915e965..a0d4398 100644
--- a/packages/annotation-comments/package.json
+++ b/packages/annotation-comments/package.json
@@ -1,6 +1,6 @@
 {
   "name": "annotation-comments",
-  "version": "0.3.0",
+  "version": "1.0.0",
   "description": "A library to parse and manipulate annotation comments in code.",
   "keywords": [],
   "author": "Tibor Schiemann",
@@ -19,7 +19,9 @@
     }
   },
   "types": "./dist/index.d.ts",
-  "files": ["dist"],
+  "files": [
+    "dist"
+  ],
   "scripts": {
     "build": "tsup ./src/index.ts --format esm --no-splitting --dts --sourcemap --clean",
     "coverage": "vitest run --coverage --coverage.include=src/**/*.ts --coverage.exclude=src/index.ts",