3.3.0 release

CHANGELOG.md

@@ -1,4 +1,11 @@
 # Changelog
+## 3.3.0
+
+- **Updated types for 2021-12-14 [vlovich]**
+- **Updated types for 2021.12.300 [vlovich]**
+- **Updated types for 2021.12.100 [vlovich]**
+- **Adds env.ASSETS.fetch typings [@GregBrimble][pull/157]**
+- **Adding missing types in RequestInitCfPropertiesImage [@itsmatteomanf][pull/156]**
 
 ## 3.2.0
 

RELEASE_CHECKLIST.md

@@ -6,23 +6,16 @@ This is a list of the things that need to happen during a release.
 
 ### Prepare the Changelog
 
-1. Open the associated milestone. All issues and PRs should be closed. If
-   they are not you should reassign all open issues and PRs to future
-   milestones.
-1. Go through the PR history since the last release. Ensure that all PRs
-   that have landed are marked with the milestone. You can use this to
-   show all the PRs that are merged on or after YYY-MM-DD:
-   `https://github.com/issues?q=repo%3Acloudflare%2Fworkers-types+merged%3A%3E%3DYYYY-MM-DD`
-1. Add this release to `CHANGELOG.md`. Use the structure of previous
-   entries.
-1. Go through the closed PRs in the milestone. For each, add an entry to
-   `CHANGELOG.md`.
+1. Go through the PR history since the last release. You can use this to show all the PRs that are merged on or after
+   YYY-MM-DD: `https://github.com/issues?q=repo%3Acloudflare%2Fworkers-types+merged%3A%3E%3DYYYY-MM-DD`
+1. Add this release to `CHANGELOG.md`. Use the structure of previous entries.
 
 ### Start a release PR
 
 1. Create a new branch "#.#.#" where "#.#.#" is this release's version (release) or "#.#.#-rc.#" (release candidate)
 1. Update the version number in `package.json`.
-1. Push up a commit with the `CHANGELOG.md` changes. The commit message can just be "#.#.#" (release) or "#.#.#-rc.#" (release candidate)
+1. Push up a commit with the `CHANGELOG.md` changes. The commit message can just be "#.#.#" (release) or "#.#.#-rc.#"
+   (release candidate)
 1. Request review from maintainers.
 
 ### Review
@@ -40,7 +33,8 @@ Most of your comments will be about the changelog. Once the PR is finalized and
 
 ### Edit the release
 
-Draft a new release on the [releases page](https://github.com/cloudflare/workers-types/releases) and update release notes.
+Draft a new release on the [releases page](https://github.com/cloudflare/workers-types/releases) and update release
+notes.
 
 ### Publish to npm
 
@@ -51,11 +45,13 @@ Full releases are tagged `latest`. If for some reason you mix up the commands be
 
 ## Troubleshooting a release
 
-Mistakes happen. Most of these release steps are recoverable if you mess up. The goal is not to, but if you find yourself cursing a fat fingered command, here are some troubleshooting tips. Please feel free to add to this guide.
+Mistakes happen. Most of these release steps are recoverable if you mess up. The goal is not to, but if you find
+yourself cursing a fat fingered command, here are some troubleshooting tips. Please feel free to add to this guide.
 
 ### I pushed the wrong tag
 
-Tags and releases can be removed in GitHub. First, [remove the remote tag](https://stackoverflow.com/questions/5480258/how-to-delete-a-remote-tag):
+Tags and releases can be removed in GitHub. First,
+[remove the remote tag](https://stackoverflow.com/questions/5480258/how-to-delete-a-remote-tag):
 
 ```console
 $ git push --delete origin tagname

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cloudflare/workers-types",
-  "version": "3.2.0",
+  "version": "3.3.0",
   "description": "TypeScript typings for Cloudflare Workers",
   "repository": {
     "type": "git",