@skirbi/tur 0.0.1 → 0.0.2

package/Changes

@@ -1,5 +1,9 @@
 Revision history for @skirbi/tur
 
+0.0.2       2026-07-01 04:09:16Z
+
+  * Bump deps
+
 0.0.1       2026-06-08 01:43:28Z
 
-    * First release to an unsuspecting world
+  * First release to an unsuspecting world

package/README.md

@@ -6,46 +6,9 @@ SPDX-License-Identifier: MIT
 
 # Welcome to @skirbi/tur
 
-Skirbi integration for Laravel projects
+This is a meta package for @skirbi. Depending on this package will ensure you
+don't need to depend on @skirbi, this package will take care of the deps.
 
-## Development
-
-Try to keep functions small and try not to depend on any outside functions. We
-aim to keep the dependency graph as small as possible. The use of `esm` is
-welcomed and writing tests is encouraged.
-
-### jsdoc
-
-You can build the documentation by running `npm run jsdoc`.
-
-### eslint
-
-The ES Linting profile is flexible and does not try to enforce much. There is
-more than one way to do it ([TIMTOWTDI](https://en.wikipedia.org/wiki/There%27s_more_than_one_way_to_do_it)).
-
-Try to stay constistent, but forcing a programming style upon others is bad.
-
-### Code of Conduct
-
-Be human.
-
-### Semver
-
-This project does not adhere to semver and one should not rely on the version
-x.y.z notation to infer stability or reliability. Read the Changes file to see
-any updates a version may bring. The fact that this module sits currently at
-0.x.z ranges does not indicate alpha or beta or even unstable associations. It
-is just a number and we started at 0.0.1.
-
-In general the following hard guarantee will be given: We will not break your
-code. In case we do happen to cause breakage: we will fix it accordingly.
-
-In case we foresee breaking changes we'll add deprecation warnings. Giving you
-time to fix things before a breaking change will be introduced. When a change
-will be introduced is communicated in the Changes file. Security fixes may
-cause breakage at any given time without notice.
-
-This package is released by `rzilla`, changes to `package.json` will be
-overridden. In addition to a little bit of promotion, this also means that
-version numbers are autoincremented at release time and bumped in all relevant
-files: Versioning for humans, not machines.
+It takes care of overrides, so all @skirbi units will only be hoisted once, you
+won't have three versions of sugar just because you depend on dibuho, semtic
+and sugar itself.

package/lib/index.mjs

@@ -2,4 +2,4 @@
 //
 // SPDX-License-Identifier: MIT
 
-const VERSION = "0.0.1";
+const VERSION = "0.0.2";

package/package.json

@@ -4,10 +4,11 @@
     "name": "Wesley Schwengle"
   },
   "dependencies": {
-    "@skirbi/dibuho": ">=0.0.1",
-    "@skirbi/pinta": ">=0.0.17",
-    "@skirbi/semtic": ">=0.0.20",
-    "@skirbi/sugar": ">=0.1.6"
+    "@skirbi/dibuho": ">=0.0.3",
+    "@skirbi/pinta": ">=0.0.19",
+    "@skirbi/semtic": ">=0.0.25",
+    "@skirbi/sugar": ">=0.1.10",
+    "@skribi/bolbe": ">=0.0.3"
   },
   "description": "Skirbi meta package",
   "devDependencies": {},
@@ -22,7 +23,7 @@
   "license": "MIT",
   "name": "@skirbi/tur",
   "overrides": {
-    "@skirbi/sugar": ">=0.1.6"
+    "@skirbi/sugar": ">=0.1.10"
   },
   "private": false,
   "scripts": {
@@ -33,5 +34,5 @@
   },
   "sideEffects": false,
   "type": "module",
-  "version": "0.0.1"
+  "version": "0.0.2"
 }