Cherry-pick security updates and patches from main to 1.1 branch

.github/workflows/build-targets.yaml

@@ -5,7 +5,7 @@ on:
 jobs:
   build:
     name: Build Code Editor Targets
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     strategy:
       matrix:
         build-target: [code-editor-server, code-editor-sagemaker-server, code-editor-web-embedded, code-editor-web-embedded-with-terminal]

.github/workflows/update-automation.yaml

@@ -216,6 +216,18 @@ jobs:
         run: |
           git config user.name "github-actions[bot]"
           git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Setup swap
+        run: |
+          # Remove existing swap if present
+          sudo swapoff -a || true
+          sudo rm -f /swapfile /mnt/swapfile || true
+          # Create new swap
+          sudo fallocate -l 12G /mnt/swapfile
+          sudo chmod 600 /mnt/swapfile
+          sudo mkswap /mnt/swapfile
+          sudo swapon /mnt/swapfile
+          free -h
 
       - name: Build target
         env:

RELEASE.md

@@ -15,18 +15,25 @@ We use major.minor branches (e.g., `1.0`, `1.1`, `2.1`) for releases.
 
 ### Release Process
 
-1. **Determine version**: Choose tag name based on the commit's branch
+1. **Determine Code Editor Version**: Choose tag name based on the commit's branch
    - Tag format: `major.minor.patch` matching the branch the commit belongs to
    - Example: Commit on `1.0` branch → tag `1.0.0`, `1.0.1`, etc.
+   - Pre-release candidates have a tag suffix as `rc.{release_candidate_version}`. For example `1.0.4-rc.1` or `1.0.4-rc.2`.
 
-2. **Create tag**: Choose one of these methods:
+2. **Determine SageMaker Code Editor Version**: 
+   - Get in touch with the SageMaker team to decide what SageMaker version needs to be used for the latest release.
+   - Hard-code that version in the patch `patches/sagemaker/display-both-versions-in-about.diff` in `product.json`.
+
+
+3. **Create release**:
    - **Command line**: Push tag to trigger release workflow
      ```bash
      git tag 1.0.0
      git push origin 1.0.0
      ```
-   - **GitHub Actions**: Manually run "Create release" workflow from Actions tab
-   - **GitHub UI**: Go to Releases → Create a new release
-
-3. **Release notes**: Include code-oss version information in the release description
+   - The workflow will:
+     - Fetch build artifacts for that commit
+     - Inject Code Editor version from the release tag into product.json
+     - Create GitHub release
 
+4. **Release notes**: Include code-oss version and Sagemaker Code Editor Version information in the release description. Release description can be edited once the release workflow creates the release. 

build-tools/oss-attribution/excluded-packages.json

@@ -1,4 +1,7 @@
 {
   "code-oss-dev@1.101.2": "UNLICENSED",
-  "jschardet@3.1.4": "LGPL-2.1-or-later"
+  "jschardet@3.1.4": "LGPL-2.1-or-later",
+  "chownr@3.0.0": "BlueOak-1.0.0",
+  "tar@7.5.4": "BlueOak-1.0.0",
+  "yallist@5.0.0": "BlueOak-1.0.0"
 }