Skip to content

fix(deps): update dependency blockly to v13#3619

Open
renovate[bot] wants to merge 1 commit into
developfrom
renovate/blockly-13.x
Open

fix(deps): update dependency blockly to v13#3619
renovate[bot] wants to merge 1 commit into
developfrom
renovate/blockly-13.x

Conversation

@renovate

@renovate renovate Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
blockly (source) ^12.4.1 → ^13.0.0 age confidence

Release Notes

RaspberryPiFoundation/blockly (blockly)

v13.0.0

Compare Source

Hello Block Builders! We have a very exciting release for you with v13.0.0! Highlights:

  • Blockly is now both keyboard-navigable and screenreader-accessible by default! You can read more about our approach here. If you have custom blocks and/or fields, you'll want to update the aria roles and labels for those as described here. See below for more resources.
  • If you were using the @blockly/keyboard-navigation plugin, you should uninstall it at the same time that you update to v13! Keyboard navigation is enabled by default.
  • As usual, each of the breaking changes PRs linked below contains instructions for how to know if a change affects you and what to do if it does. Many of these breaking changes are quite niche so for many of you it should not be a huge lift to update. A big category of these is the addition of new keyboard navigation shortcuts. If these conflict with your existing shortcuts, you'll need to update one or the other. We recommend you keep our default keyboard navigation shortcuts if at all possible, to maintain parity with other block-based applications. Get in touch on the forum if you have questions!
  • We updated the default renderer to thrasos. If you explicitly specify your renderer (as you probably should) then this does not affect you, but if not you may notice your blocks look very slightly different. Thrasos is more performant than geras so we recommend you keep using it if possible.
  • We've added a new sound for when a block is dropped on the workspace. Our user testing validated that the new sound helped users understand when a new block is placed, in addition to the existing sound effect for when blocks are connected or disconnected. We know new sounds can be jarring but give it a chance :)
  • We also updated the default location of sounds to blockly.com/media. Best practice is to host the sounds yourself, so if you're doing that be sure to also host the new sound. Or you can replace it with your own file if you prefer.
  • The oldest browser we now support is Safari 15.4. This version is already no longer receiving security updates from Apple so we believe most applications should already have a minimum supported version newer than this. If this is an issue for you, you can polyfill the css :has selector and continue supporting older versions.
  • Plugins are coming soon - we'll send another email when they're released. New this cycle is that all plugins will receive the v13.0.0 version number so it will be easy to tell how to update your plugins when required.

More accessibility resources:

  • Be on the lookout for our Blockly Summit 2026 talks on YouTube which had tons of relevant talks! We'll post an update on the forum when these are live.
  • Best practices for creating accessible applications
  • How to audit your block-based app for conformance with accessibility requirements

What's Changed

Breaking changes 🛠
New features ✨
Bug fixes 🐛
Documentation updates 📄

New Contributors

Full Changelog: RaspberryPiFoundation/blockly@blockly-v12.5.1...blockly-v13.0.0

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Jun 18, 2026
@renovate

renovate Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @blockly/continuous-toolbox@7.0.9
npm error Found: blockly@13.0.0
npm error node_modules/blockly
npm error   blockly@"^13.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer blockly@"^12.0.0" from @blockly/continuous-toolbox@7.0.9
npm error node_modules/@blockly/continuous-toolbox
npm error   @blockly/continuous-toolbox@"^7.0.8" from the root project
npm error
npm error Conflicting peer dependency: blockly@12.5.1
npm error node_modules/blockly
npm error   peer blockly@"^12.0.0" from @blockly/continuous-toolbox@7.0.9
npm error   node_modules/@blockly/continuous-toolbox
npm error     @blockly/continuous-toolbox@"^7.0.8" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-06-18T20_01_39_194Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-18T20_01_39_194Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants