Bump version to 1.1.2 and work around softprops/action-gh-release's incompatibility with immutable releases (#286)

Author: agriyakhetarpal

.github/workflows/cd.yml

@@ -1,8 +1,9 @@
 name: CD
 
 on:
-  release:
-    types: [published]
+  push:
+    tags:
+      - 'v*'
   schedule:
     - cron: '0 0 * * 0' # Every Sunday at midnight UTC
   workflow_dispatch:
@@ -43,7 +44,7 @@ jobs:
     name: Package and upload to GitHub Release
     runs-on: ubuntu-latest
     needs: build-app
-    if: github.event_name == 'release' && github.event.action == 'published'
+    if: startsWith(github.ref, 'refs/tags/')
     permissions:
       # Required to upload artifacts to a GitHub release identifier
       contents: write
@@ -81,8 +82,14 @@ jobs:
               gh attestation verify "${artifact}" --repo $GH_REPO
           done
 
-      - name: Publish to GitHub Release
+      - name: Upload release assets with a draft release
         uses: softprops/action-gh-release@51cfd90a6d81cfe329568f851fe2236ab4416d17 # v2.2.0
-        if: github.event_name == 'release' && github.event.action == 'published'
         with:
           files: upload/*
+          draft: true
+
+      - name: Publish final release
+        uses: softprops/action-gh-release@51cfd90a6d81cfe329568f851fe2236ab4416d17 # v2.2.0
+        with:
+          generate_release_notes: true
+          draft: false

RELEASE.md

@@ -7,12 +7,12 @@ We release the extension bundled with the full JupyterLite application files as
 
 ```bash
 git tag -s vX.Y.Z -m "Release vX.Y.Z"
-git push vX.Y.Z
+git push origin vX.Y.Z # set the remote name and branch as appropriate, if contributing from a fork or other remote
 ```
 
-3. Create a new release on GitHub, using the tag created in the previous step. This will trigger the `.github/workflows/cd.yml`
-   workflow, which will build the extension, install it, install JupyterLite, build the JupyterLite static assets, and create
-   a tarball with the resulting files. The tarball will be attached to the GitHub Release.
+3. The push will trigger the `.github/workflows/cd.yml` workflow, which will build the extension, install it, install JupyterLite,
+   build the JupyterLite static assets, and create a tarball with the resulting files. The tarball will be attached to a draft
+   GitHub Release. The workflow will then publish the release automatically.
 
 4. You may verify that the attached tarball contains the expected files, and proceed to deploy it with the sharing service
    in [the `jupytereverywhere/infrastructure` repository](https://github.com/JupyterEverywhere/infrastructure).

package.json

@@ -1,6 +1,6 @@
 {
     "name": "jupytereverywhere",
-    "version": "1.1.1",
+    "version": "1.1.2",
     "description": "A Jupyter extension for k12 education",
     "keywords": [
         "jupyter",

ui-tests/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jupytereverywhere-ui-tests",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "description": "Jupyter Everywhere Integration Tests",
   "private": true,
   "scripts": {