From b1edd926db57cd3b5e1a968cd048d39f23f30a0d Mon Sep 17 00:00:00 2001
From: "Aaron (Qilong)" <173288704@qq.com>
Date: Fri, 20 Sep 2024 11:37:51 -0400
Subject: [PATCH] Update pkg.json (#56)

---
 TuneUp/manifests/pkg.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/TuneUp/manifests/pkg.json b/TuneUp/manifests/pkg.json
index 1810a38..ea2b588 100644
--- a/TuneUp/manifests/pkg.json
+++ b/TuneUp/manifests/pkg.json
@@ -2,7 +2,7 @@
   "license": "",
   "file_hash": null,
   "name": "TuneUp",
-  "version": "1.0.10",
+  "version": "1.0.11",
   "description": "*** THE TUNEUP EXTENSION USES NEW API FEATURES THAT ARE ONLY AVAILABLE IN DYNAMO VERSION 2.5 OR ABOVE ***\r\n\r\nTuneUp is in beta and is a view extension for analyzing the performance of Dynamo graphs. TuneUp allows you to see overall graph execution time, per-node execution time, and other helpful information about what's happening under the hood, e.g. nodes run in the current execution v.s. nodes run in the previous execution (which are skipped this run for optimization/ caching). Read more here: https://dynamobim.org/tuneup-extension-explore-your-node-and-graph-execution-times/ \r\n\r\nKnown issues:\r\n1. TuneUp does not work with .dyfs (custom nodes) yet.\r\n2.TuneUp binaries are not semantically versioned and are not intended to be built on top of as an API. Do not treat these binaries like DynamoCore.\r\n3. TuneUp requires Dynamo 3.0 or higher for access to new extension APIs.\r\n4. When user have TuneUp open, after switching workspace in Dynamo, the first graph run does not give execution time and nodes order.",
   "group": "",
   "keywords": [
@@ -19,4 +19,4 @@
   "repository_url": "https://github.com/DynamoDS/TuneUp",
   "contains_binaries": true,
   "node_libraries": []
-}
\ No newline at end of file
+}