# Dfx 0.11.2 is promoted **URL:** \ **Category:** Developers\ **Tags:** release, sdk\ **Created:** [August 31, 2022, 2:32pm UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210 "2022-08-31T14:32:22Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![mnl](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/mnl/32/5909_2.png) [@mnl](https://forum.dfinity.org/u/mnl)\ **Post date:** [August 31, 2022, 2:32pm UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/1 "2022-08-31T14:32:22Z")
[Release Notes | Internet Computer Home](https://internetcomputer.org/docs/current/developer-docs/updates/release-notes/) ## Summary - Patch release for frontend canister (also known as asset canister or certified assets canister) code. - Recent updates to the asset canister that came as part of `dfx 0.11.1` release introduced two unwanted behaviors to asset canister code, and we’re disabling both of them with this release: 1. redirection of all HTTP traffic from `.raw.ic0.app` to `.ic0.app` - HTTP traffic redirection will find its way into `dfx` in the form of per-asset configurable redirects in the upcoming `dfx` release 2. support for `ETag` HTTP header (a mechanism to aid cache validation). - `ETag's will be back once we add more code to `icx-proxy` I know those two issues broke workflows for some people, for which I’m sorry, as this slipped through the release review process I was conducting. We will be implementing measures to make sure this never happens again. Happy building! ---
**Author:** ![dymayday](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dymayday/32/4935_2.png) [@dymayday](https://forum.dfinity.org/u/dymayday)\ **Post date:** [September 1, 2022, 9:43am UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/2 "2022-09-01T09:43:35Z")
Arf, you still cannot use `dfx deploy` with Gzipped wasm 😕 (When the path to the wasm.gz is specified in dfx.json) Sticking with version 0.10.1 then, but thanks for the hard work ! Maybe in version 0.12 🤞🙂🤞 ---
**Author:** ![mnl](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/mnl/32/5909_2.png) [@mnl](https://forum.dfinity.org/u/mnl)\ **Post date:** [September 1, 2022, 10:56am UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/3 "2022-09-01T10:56:11Z")
0.12.0 will support gzipped wasm 🙂 ---
**Author:** ![dansteren](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dansteren/32/1048_2.png) [@dansteren](https://forum.dfinity.org/u/dansteren)\ **Post date:** [September 1, 2022, 3:32pm UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/4 "2022-09-01T15:32:26Z")
There’s an open issues you can follow for this: [dfx deploy with gzip · Issue #2357 · dfinity/sdk · GitHub](https://github.com/dfinity/sdk/issues/2357). I’m looking forward to it as well 🙂 ---
**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:** [September 1, 2022, 4:06pm UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/5 "2022-09-01T16:06:43Z")
Does this have the latest motoko updates demoed in the Global R&D? ---
**Author:** ![mnl](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/mnl/32/5909_2.png) [@mnl](https://forum.dfinity.org/u/mnl)\ **Post date:** [September 1, 2022, 4:19pm UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/6 "2022-09-01T16:19:17Z")
Features presented at yesterday’s Global R&D are not part of 0.11.2 release. 0.11.2 is only a patch release to frontend canister code (wasm), there were no other changes in comparison to 0.11.1. Looks like some of the features from yesterday GR&D are part of [Release 0.7.0 · dfinity/motoko · GitHub](https://github.com/dfinity/motoko/releases/tag/0.7.0) (tho I don’t know if that release includes all of the features presented). At the time of writing this message, `master` branch of `dfx` uses motoko 0.6.3, and I don’t know/can’t promise if 0.7.0 motoko will get included in next dfx minor release (0.12.0). - the best place to check for that information is go to `master` on sdk repo, and visit section [Unreleased\>\>Dependencies in CHANGELOG.md](https://github.com/dfinity/sdk/blob/master/CHANGELOG.md#dependencies) - also search for pull requests by `motoko` keyword [https://github.com/dfinity/sdk/pulls?q=motoko](https://github.com/dfinity/sdk/pulls?q=motoko) ---
**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:** [September 4, 2022, 1:25pm UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/7 "2022-09-04T13:25:37Z")
Nope, but you can manually download `moc` and put it in (if you are into patching or sufficiently desperate). ---
**Author:** ![karim](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/karim/32/4680_2.png) [@karim](https://forum.dfinity.org/u/karim)\ **Post date:** [September 21, 2022, 11:00am UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/8 "2022-09-21T11:00:29Z")
After upgrading to 0.11.2 dfx complained about duplicate asset keys. I removed the `CopyPlugin()` as described [here](https://internetcomputer.org/docs/current/developer-docs/updates/release-notes/#duplicate-asset-keys-are-now-reported-as-errors) and also deleted the /dist folder from my project. However, now my React application can’t find the asset files including the main.css anymore. What is the recommended way for adding static assets now with 0.11.2? ---
**Author:** ![mnl](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/mnl/32/5909_2.png) [@mnl](https://forum.dfinity.org/u/mnl)\ **Post date:** [September 21, 2022, 3:12pm UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/9 "2022-09-21T15:12:51Z")
It’s difficult for me to say what’s the root cause in this case, perhaps you can share the content of your: `dfx.json`, `package.json`, `webpack.config.js`? The recommended way of adding static assets has not changed – when you issue `dfx new xyz`, the directory for frontend project will contain `src/xyz_frontend/src` and `src/xyz_frontend/assets`. Webpack config file is set up in way which will bundle the content of `src/xyz_frontend/src` into `/dist` directory. Afterwards, when you `dfx deploy` your canister, `dfx` will upload all files in directories listed under the key `canisters.xyz_frontend.source` in `dfx.json` file. ---
**Author:** ![karim](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/karim/32/4680_2.png) [@karim](https://forum.dfinity.org/u/karim)\ **Post date:** [September 21, 2022, 9:43pm UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/10 "2022-09-21T21:43:49Z")
Thanks for your answer! I created a new project with `dfx new ` and compared the `webpack.config.js`. The following line was missing in the config of my old project: `static: path.resolve(__dirname, "src", frontendDirectory, "assets")`. Added it in and now it’s working again. ---
**Author:** ![mnl](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/mnl/32/5909_2.png) [@mnl](https://forum.dfinity.org/u/mnl)\ **Post date:** [September 22, 2022, 9:30am UTC](https://forum.dfinity.org/t/dfx-0-11-2-is-promoted/15210/11 "2022-09-22T09:30:32Z")
glad to hear you’ve figured it out!