Code classroom v15

.github/path-filters.yml

@@ -1,3 +1,7 @@
+# This file is generated by scripts/update-gha-workflows.ts
+#
+# To regenerate:  npm run refresh-gh-workflow
+
 # The `&global` anchor defines a set of common paths to include by reference in the other filters.
 global: &global
   - ".github/path-filters.yml"
@@ -14,24 +18,37 @@ any-workspace:
 task-herder:
   - *global
   - "packages/task-herder/**"
-scratch-media-lib-scripts:
+scratch-storage:
   - *global
-  - "packages/scratch-media-lib-scripts/**"
+  - "packages/scratch-storage/**"
+  - "packages/task-herder/**"
 scratch-svg-renderer:
   - *global
   - "packages/scratch-svg-renderer/**"
+scratch-paint:
+  - *global
+  - "packages/scratch-paint/**"
+  - "packages/scratch-svg-renderer/**"
 scratch-render:
   - *global
   - "packages/scratch-render/**"
   - "packages/scratch-svg-renderer/**"
 scratch-vm:
   - *global
   - "packages/scratch-render/**"
+  - "packages/scratch-storage/**"
   - "packages/scratch-svg-renderer/**"
   - "packages/scratch-vm/**"
+  - "packages/task-herder/**"
 scratch-gui:
   - *global
   - "packages/scratch-gui/**"
+  - "packages/scratch-paint/**"
   - "packages/scratch-render/**"
+  - "packages/scratch-storage/**"
   - "packages/scratch-svg-renderer/**"
   - "packages/scratch-vm/**"
+  - "packages/task-herder/**"
+scratch-media-lib-scripts:
+  - *global
+  - "packages/scratch-media-lib-scripts/**"

.github/workflows/ci.yml

@@ -103,7 +103,7 @@ jobs:
         env:
           NPM_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
-          RELEASE_VERSION="13.7.3-code-classroom.$(date +'%Y%m%d%H%M%S')"
+          RELEASE_VERSION="15.1.1-code-classroom.$(date +'%Y%m%d%H%M%S')"
           npm version --no-git-tag-version "$RELEASE_VERSION"
           npm publish --access public --tag latest --ignore-scripts
 

.gitignore

@@ -1,7 +1,6 @@
-# build-monorepo.sh
-/monorepo.out
-/monorepo.tmp
-/monorepo.cache
+# add-repo.sh
+/add-repo.tmp
+/add-repo.errors.log
 
 # Logs
 logs

.nvmrc

@@ -1 +1 @@
-24.15.0
+24.20.0

CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

README.md

@@ -17,7 +17,7 @@ This repository is a public fork of [scratchfoundation/scratch-editor](https://g
 | | |
 |---|---|
 | **Upstream anchor branch** | [`code-classroom-base`](https://github.com/RaspberryPiFoundation/scratch-editor/tree/code-classroom-base) — points at a [scratchfoundation/scratch-editor](https://github.com/scratchfoundation/scratch-editor) **release tag** only (no RPF packaging) |
-| **Upstream release** | [`v13.7.3`](https://github.com/scratchfoundation/scratch-editor/releases/tag/v13.7.3) (current tag on `code-classroom-base`) |
+| **Upstream release** | [`v15.1.1`](https://github.com/scratchfoundation/scratch-editor/releases/tag/v15.1.1) (current tag on `code-classroom-base`) |
 | **Integration branch** | [`code-classroom`](https://github.com/RaspberryPiFoundation/scratch-editor/tree/code-classroom) — long-lived branch; RPF packaging, CI, and feature work merge here via PR |
 | **RPF changes (diff)** | [Compare `code-classroom` to `code-classroom-base`](https://github.com/RaspberryPiFoundation/scratch-editor/compare/code-classroom-base...code-classroom) — packaging, CI, and fork-only code |
 | **Published package** | [`@RaspberryPiFoundation/scratch-gui`](https://github.com/RaspberryPiFoundation/scratch-editor/pkgs/npm/scratch-gui) on GitHub Packages |
@@ -64,7 +64,7 @@ npm start   # http://localhost:8601/
 ### CI and publishing
 
 - **Pull requests:** CI runs build and tests; **no** package is published to GitHub Packages.
-- **Push to `code-classroom`:** CI builds and publishes `@RaspberryPiFoundation/scratch-gui` with a version such as `13.7.3-code-classroom.YYYYMMDDHHMMSS`. Pin an explicit version in consumers (e.g. editor-ui); do not rely on floating `latest` in production.
+- **Push to `code-classroom`:** CI builds and publishes `@RaspberryPiFoundation/scratch-gui` with a version such as `15.1.1-code-classroom.YYYYMMDDHHMMSS`. Pin an explicit version in consumers (e.g. editor-ui); do not rely on floating `latest` in production.
 - Publishing is configured in [`.github/workflows/ci.yml`](.github/workflows/ci.yml) (inline publish step on the `code-classroom` branch only). Upstream’s npmjs release workflow (`.github/workflows/publish.yml`) is disabled on this fork.
 
 ## What's in this repository?
@@ -73,9 +73,14 @@ The `packages` directory in this repository contains:
 
 - `scratch-gui` provides the buttons, menus, and other elements that you interact with when creating and editing a
   project. It's also the "glue" that brings most of the other modules together at runtime.
+- `scratch-media-lib-scripts` builds (or rebuilds) media libraries for the editor.
+- `scratch-paint` provides a way to draw vector (SVG) or bitmap (PNG) images for costumes and backdrops.
 - `scratch-render` draws backdrops, sprites, and clones on the stage.
+- `scratch-storage` helps load project assets like images and sounds. It also provides `ScratchFetch`, a customized
+  wrapper around `fetch`.
 - `scratch-svg-renderer` processes SVG (vector) images for use with Scratch projects.
 - `scratch-vm` is the virtual machine that runs Scratch projects.
+- `task-herder` manages queues of tasks with throttling and concurrency limits.
 
 _Please add to this list as more packages are migrated to the monorepo._
 

Release.md

@@ -2,16 +2,44 @@
 
 _For maintainers of this monorepo._
 
-All packages in this monorepo will be published to NPM when a new release is created. They'll all share the same
-version number. To create a new release:
-
-1. Select "Draft a new release" from [the repository's "Releases"
-   tab](https://github.com/scratchfoundation/scratch-editor/releases) or "Create a new release" from [the main page of
-   the repository](https://github.com/scratchfoundation/scratch-editor/).
-2. To create a tag for the release, select the **Choose a tag** dropdown menu, type a version number for your release,
-   then click **Create new tag**. The tag of the release is used to determine and update package versions.
-3. In the **Describe this release** field, type a description for your release. If you @mention anyone in the
-   description, the published release will include a Contributors section with an avatar list of all the mentioned
-   users. Alternatively, you can automatically generate your release notes by clicking **Generate release notes**.
-   This provides a list with the **Pull Requests** included in the release and their creators.
-4. Clicking **Publish release** triggers the publishing workflow that will publish the monorepo packages to NPM.
+All packages in this monorepo are published to npm with a shared version number. Releases are produced by the
+**Publish** workflow, triggered manually from the Actions tab. The next version number and the changelog are
+both computed from the Conventional Commits on the release branch.
+
+## Releasing
+
+1. Push the commits you want included to the branch you want to release from.
+2. Open the [Publish workflow](https://github.com/scratchfoundation/scratch-editor/actions/workflows/publish.yml).
+3. Click the **Run workflow** dropdown, choose the branch, and click the **Run workflow** button.
+4. Wait for the workflow to finish. On success: the packages are on npm, a tag and GitHub release exist, and
+   the version-bump commit is on the branch.
+
+If there are no relevant commits since the last release on that branch, the workflow exits cleanly with a
+"nothing to publish" notice. Pressing the button on a branch with only `chore:` or `docs:` commits is a no-op.
+
+## Which branches can release
+
+| Branch                 | Acts as                | npm dist-tag      | Example version          |
+|------------------------|------------------------|-------------------|--------------------------|
+| `develop`              | primary release        | `latest`          | `13.8.0`                 |
+| `13.x`, `13.7.x`, etc. | maintenance            | matching the line | `13.7.5`                 |
+| `release/<topic>`      | long-lived prerelease  | `<topic>`         | `13.8.0-accessibility.3` |
+| `hotfix/<topic>`       | short-lived prerelease | `<topic>`         | `13.7.5-paint-fix.1`     |
+
+The dist-tag for `release/*` and `hotfix/*` is the branch name with the prefix stripped. Pick a short, public-
+facing branch suffix — it becomes the dist-tag downstream consumers see.
+
+Other branches (`feat/*`, `fix/*`, `chore/*`, `feature/*`, bare names) are not releasable. The workflow run
+will fail at the branch-validation step.
+
+## Conventional Commits matter
+
+Version bumps are computed from commit types:
+
+- `fix:` → patch
+- `feat:` → minor
+- `BREAKING CHANGE:` in the body (or `!:` in the header) → major
+- `chore:`, `docs:`, `style:`, `refactor:`, `test:`, `ci:`, `build:` → no release
+
+A wrong commit type means a wrong version bump. The husky hook enforces the format, but it's up to you to categorize
+your commit correctly.