From c5353e1f3c9385c35f64e838a0a09dc4bb8f7b07 Mon Sep 17 00:00:00 2001
From: X <i@jex.me>
Date: Tue, 27 Dec 2022 19:19:17 +0800
Subject: [PATCH] V101

---
 CHANGELOG.md     | 5 +++++
 README.md        | 2 +-
 server/consts.go | 2 +-
 3 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 48b2bc023..c09342103 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,10 @@
 # Change Log
 
+## v101
+
+- Fix `?bundle` mode with illegal paths (close [#476](https://github.com/ije/esm.sh/issues/476)).
+- Fix `?worker` mode doesn't support CORS.
+
 ## v100
 
 - Improve self-hosting configuration. check [HOSTING.md](./HOSTING.md) for more details.
diff --git a/README.md b/README.md
index 0f13c1605..597c1a289 100644
--- a/README.md
+++ b/README.md
@@ -208,7 +208,7 @@ import unescape from "https://esm.sh/lodash/unescape?no-dts"
 Since we update esm.sh server frequently, sometime we may break packages that work fine previously by mistake, the server will rebuild all modules when the patch pushed. To avoid this, you can **pin** the build version by the `?pin=BUILD_VERSON` query. This will give you an **immutable** cached module.
 
 ```javascript
-import React from "https://esm.sh/react@17.0.2?pin=v100"
+import React from "https://esm.sh/react@17.0.2?pin=v101"
 ```
 
 ## Global CDN
diff --git a/server/consts.go b/server/consts.go
index dd934efe4..4e5412fb6 100644
--- a/server/consts.go
+++ b/server/consts.go
@@ -2,7 +2,7 @@ package server
 
 const (
 	// esm.sh build version
-	VERSION          = 100
+	VERSION          = 101
 	nodejsMinVersion = 16
 	denoStdVersion   = "0.170.0"
 	nodejsLatestLTS  = "16.18.1"