# Upcoming changes in Motoko 0.11.0

**URL:** <https://forum.dfinity.org/t/upcoming-changes-in-motoko-0-11-0/28218>\
**Category:** Developers\
**Created:** [March 7, 2024, 3:10pm UTC](https://forum.dfinity.org/t/upcoming-changes-in-motoko-0-11-0/28218 "2024-03-07T15:10:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dfx-json](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dfx-json/32/4784_2.png) [@dfx-json](https://forum.dfinity.org/u/dfx-json)\
**Post date:** [March 7, 2024, 3:10pm UTC](https://forum.dfinity.org/t/upcoming-changes-in-motoko-0-11-0/28218/1 "2024-03-07T15:10:23Z")

</div>

Hello everyone. Earlier this week, the Motoko team shipped the v0.11.0 version of Motoko. In addition to a few [minor improvements](https://github.com/dfinity/motoko/blob/master/Changelog.md), like the `Option.equal` method, and warnings for unused identifiers, a new safety mechanism was introduced that could cause breaking changes to existing code.

## Overview

In previous Motoko versions, third-party library functions could make calls to sensitive functions such as `ExperimentalCycles.add(...)` and `Timer.setTimer(...)` without providing any indication to the caller that sensitive system functionality was being used.

In Motoko 0.11.0 and newer, the type system is used to detect and prevent this scenario while still allowing developers to grant access to sensitive functions.

## Migration

You can find the migration guide here: [https://internetcomputer.org/docs/current/developer-docs/backend/motoko/0.11.0-migration-guide/](https://internetcomputer.org/docs/current/developer-docs/backend/motoko/0.11.0-migration-guide/). Please take a look and update your code if necessary. It may be especially impactful for certain library authors or any Motoko canisters that made use of those libraries.

This change will be bundled with version 0.18.0 of `dfx`, which will be shipped by the end of the week, March 8, 2024.

If you have any questions, please drop them in the thread or email [team-motoko@dfinity.org](mailto:team-motoko@dfinity.org) directly.

---

<div class="post-metadata">

**Author:** ![skilesare](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/skilesare/32/5609_2.png) [@skilesare](https://forum.dfinity.org/u/skilesare)\
**Post date:** [March 14, 2024, 2:06pm UTC](https://forum.dfinity.org/t/upcoming-changes-in-motoko-0-11-0/28218/2 "2024-03-14T14:06:35Z")

</div>

Is there a way to turn off(and then selectively turn off) the unused identifier warning? In projects that have (msg) for every actor function as a force of habit is is a bit verbose. For projects that have legacy libraries that they don’t control, it also gets a bit out of hand. I’d love to be able to tidy up my core project, but not have to wade through the 1000+ messages in my dependent libraries.

---

<div class="post-metadata">

**Author:** ![ggreif](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/ggreif/32/301_2.png) [@ggreif](https://forum.dfinity.org/u/ggreif)\
**Post date:** [March 15, 2024, 7:07pm UTC](https://forum.dfinity.org/t/upcoming-changes-in-motoko-0-11-0/28218/3 "2024-03-15T19:07:25Z")

</div>

`moc` 0.11.1 is just out. It has 2 changes to reduce chattiness. Try swapping it in…

---

<div class="post-metadata">

**Author:** ![Samer](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/samer/32/8943_2.png) [@Samer](https://forum.dfinity.org/u/Samer)\
**Post date:** [April 28, 2024, 6:47pm UTC](https://forum.dfinity.org/t/upcoming-changes-in-motoko-0-11-0/28218/4 "2024-04-28T18:47:44Z")

</div>

Wen weekly Motoko updates again?