From f40335939e00c404d385205f4a7113e479097029 Mon Sep 17 00:00:00 2001
From: 3lpsy <8757851+3lpsy@users.noreply.github.com>
Date: Fri, 31 Jan 2025 11:46:09 -0600
Subject: [PATCH] changes meta info

---
 .changes/skip-logger.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.changes/skip-logger.md b/.changes/skip-logger.md
index b386adb4..d5066491 100644
--- a/.changes/skip-logger.md
+++ b/.changes/skip-logger.md
@@ -1,4 +1,5 @@
 ---
-'log': 'patch:enhance'
+'log': 'minor:feat'
+'log-js': 'minor:feat'
 ---
 Add a `is_skip_logger` flag to the Log Plugin `Builder` struct, a `skip_logger()` method to the Builder, and logic to avoid acquiring (creating) a logger and attaching it to the global logger. Since acquire_logger is pub, a `LoggerNotInitialized` is added and returned if it's called when the `is_skip_looger` flag is set. Overall, this feature permits a user to avoid calling `attach_logger` which can only be called once in a program's lifetime and allows the user to control the logger returned from `logger()`. Additionally, it also will allow users to generate multiple Tauri Mock apps in test suites that run and parallel and have the `log` plugin attached (assuming they use `skip_logger()`).