@ignatremizov/vue-tailwind-datepicker 2.1.6 → 2.1.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +5 -5
  2. package/package.json +10 -3
package/README.md CHANGED
@@ -444,10 +444,10 @@ Behavior summary:
444
444
 
445
445
  ## Dependency Pins (Dev)
446
446
 
447
- - Maintainer builds and CI workflows use Node 24.22.1 and the npm version declared in root/docs `packageManager` (12.2.1). Workflows bootstrap that exact npm version with `--ignore-scripts` before installing dependencies under the reviewed policy, including when the runner initially has npm 11. Pull requests validate install policy, lint, library declarations, types, unit tests, packaged-entry tests, and documentation builds without running release steps. This tooling pin does not narrow the library's consumer peer dependencies.
447
+ - Maintainer builds and CI workflows use Node 24.22.3 and the npm version declared in root/docs `packageManager` (12.2.2). Workflows bootstrap that exact npm version with `--ignore-scripts` before installing dependencies under the reviewed policy, including when the runner initially has npm 11. Pull requests validate install policy, lint, library declarations, types, unit tests, packaged-entry tests, and documentation builds without running release steps. This tooling pin does not narrow the library's consumer peer dependencies.
448
448
  - `@headlessui/vue` is pinned to the fork's GitHub release tarball `1.7.24-iremizov.3`, retaining the Vue fixes not yet available in the upstream npm line used by this repo. Headless UI is bundled into the published datepicker, so consumers receive this update with the next datepicker release.
449
- - `js-beautify` now resolves to registry 2.0.3 through `@vue/test-utils`' declared `^2.0.0` dependency. Its upstream dependency modernization makes the old Git security override unnecessary. Test-utils bundles its HTML formatter, and this repo has no direct Angular `@let` or escaped Unicode formatter configuration requiring the fork's additional fixes. Exact HTML, raw output, and diagnostic formatting tests passed unchanged before and after removing the override.
450
- - The npm CLI used by `@semantic-release/npm` is pinned to 12.2.1 as well. The plugin's version/pack preparation path is tested against that CLI in an isolated fixture without publishing.
449
+ - `js-beautify` resolves to registry 2.0.3 through `@vue/test-utils`' declared `^2.0.0` dependency. Its CLI's formatter dependency paths use scoped `glob@14.0.6` and `editorconfig@4.0.1` overrides, with `minimatch@11.0.8` scoped to these paths and TypeScript-ESTree. ESLint's legacy `minimatch@3` consumers and the npm CLI bundled below `@semantic-release/npm` remain unchanged. Test-utils bundles its HTML formatter, and this repo has no direct Angular `@let` or escaped Unicode formatter configuration requiring the fork's additional fixes.
450
+ - The npm CLI used by `@semantic-release/npm` is pinned to 12.2.2 as well. The plugin's version/pack preparation path is tested against that CLI in an isolated fixture without publishing.
451
451
  - The separate docs package overrides only VitePress's Vite dependency to `^6.4.5`. Stable VitePress 1.6.4 still requests Vite 5, while its Vue plugin supports Vite 6. This keeps the existing documentation setup on a patched Vite line without adopting VitePress 2 prereleases. Recheck `npm run docs:build` and the interactive `/demo.html` page when changing this override.
452
452
  - When updating the Headless UI fork pin, prefer a tagged release or commit SHA URL and run:
453
453
  - `npm install`
@@ -457,7 +457,7 @@ Behavior summary:
457
457
 
458
458
  ### Install-script policy
459
459
 
460
- Root and docs each have their own `.npmrc` and `allowScripts` policy. `strict-allow-scripts=true` rejects unreviewed dependency lifecycle scripts, and `strict-npmrc=true` rejects unknown configuration keys instead of silently ignoring a typo. Use npm 12.2.1 for maintainer installs; npm 11 does not enforce the same strict policy.
460
+ Root and docs each have their own `.npmrc` and `allowScripts` policy. `strict-allow-scripts=true` rejects unreviewed dependency lifecycle scripts, and `strict-npmrc=true` rejects unknown configuration keys instead of silently ignoring a typo. Use npm 12.2.2 for maintainer installs; npm 11 does not enforce the same strict policy.
461
461
 
462
462
  - Root approves only `esbuild@0.28.2` and `vue-demi@0.14.10`; docs approves only `esbuild@0.25.12` and `vue-demi@0.14.10`. Their scripts select/validate the platform binary and install the Vue compatibility shim, respectively.
463
463
  - Both explicitly deny `fsevents@2.3.3` install scripts. Its distributed archive includes a prebuilt native module and no build inputs or install hook, although registry metadata advertises a native rebuild. No native rebuild is needed or approved.
@@ -465,7 +465,7 @@ Root and docs each have their own `.npmrc` and `allowScripts` policy. `strict-al
465
465
 
466
466
  After changing a dependency, inspect `npm install-scripts ls` and `npm --prefix docs install-scripts ls`. Review the actual scripts before approving a specific package with `npm install-scripts approve <package>` (or the docs-prefixed command), which writes an exact-version approval by default. Update the policy deliberately when a reviewed version changes, and rerun `npm run test:npm-policy`, both clean installs, and the normal build/test gates. Do not use approve-all or disable strict enforcement to make an install pass. Root-owned project hooks, such as the library's prepack build, still run normally.
467
467
 
468
- The remaining development audit advisory is [braces stack exhaustion](https://github.com/advisories/GHSA-vfj7-8cjw-p6xm), reached through `semantic-release` and its plugins via `micromatch`. At the time of the October 2026 refresh, the latest stable parent packages still use the affected `braces` 3.0.3, and no patched version is published. The relevant patterns come from maintainer-controlled release configuration (branch patterns, release rules, and asset globs), not datepicker input. Keep release configuration trusted and recheck upstream for a fix; do not force the audit-suggested downgrade of the release plugins. Audit the runtime tree separately with `npm audit --omit=dev`, and audit documentation tooling with `npm --prefix docs audit`.
468
+ The previously reported [braces stack-exhaustion advisory](https://github.com/advisories/GHSA-vfj7-8cjw-p6xm) was withdrawn on October 23, 2026, because it was not practically exploitable. The October 25 refresh started with no findings in the full root, production-only, or separate docs dependency trees. The compatible lockfile updates are maintenance changes, not a fix for the withdrawn report, and no override or suppression was added. Continue checking the complete tree with `npm audit`, the runtime tree with `npm audit --omit=dev`, and documentation tooling with `npm --prefix docs audit`.
469
469
 
470
470
  ## Changelog
471
471
 
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@ignatremizov/vue-tailwind-datepicker",
3
3
  "type": "module",
4
- "version": "2.1.6",
5
- "packageManager": "npm@12.2.1",
4
+ "version": "2.1.8",
5
+ "packageManager": "npm@12.2.2",
6
6
  "allowScripts": {
7
7
  "esbuild@0.28.2": true,
8
8
  "fsevents@2.3.3": false,
@@ -248,7 +248,14 @@
248
248
  },
249
249
  "overrides": {
250
250
  "@semantic-release/npm": {
251
- "npm": "12.2.1"
251
+ "npm": "12.2.2"
252
+ },
253
+ "@typescript-eslint/typescript-estree": {
254
+ "minimatch": "11.0.8"
255
+ },
256
+ "js-beautify": {
257
+ "editorconfig": "4.0.1",
258
+ "glob": "14.0.6"
252
259
  }
253
260
  }
254
261
  }