Skip to content

deps: bump the minor group across 1 directory with 2 updates - #77

Merged
Shinrai merged 4 commits into
nextfrom
dependabot/npm_and_yarn/next/minor-25059ba4aa
Oct 3, 2026
Merged

Shinrai merged 4 commits into
nextfrom
dependabot/npm_and_yarn/next/minor-25059ba4aa

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 2, 2026 •

Copy link
Copy Markdown

Bumps the minor group with 2 updates in the / directory: @cldmv/vitest-runner and typescript-eslint.

Updates @cldmv/vitest-runner from 1.4.3 to 1.5.1

Release notes

Sourced from @​cldmv/vitest-runner's releases.

v1.5.1

release: v1.5.1 - backfill the missing v1.5.0 changelog

vitest-runner v1.5.1 Changelog

Release Date: September 2026 Release Type: Patch Branch: release/1.5.1


Overview

A documentation-only release: v1.5.0 shipped through the automated release-merge gate before its changelog and README What's New update had landed on next, so it released with the raw auto-generated PR-title dump instead of curated notes. This backfills v1.5.0's changelog and promotes the README. No code changes.


📚 Documentation

Backfilled the missing v1.5.0 changelog

docs/changelog/v1/v1.5.0.md — the curated release notes for the exclude option (#57, #58) that v1.5.0 shipped without. The README ✨ What's New block is promoted to match.


Upgrade notes

No breaking changes — drop-in for v1.5.0. No runtime code changed.


coverage

Metric Coverage
Statements 99.6%
Branches 100.0%
Functions 100.0%
Lines 99.6%

Avg: 99.8% · d915e7d · Node lts/*

... (truncated)

Commits
  • 7aedb32 release: v1.5.1 - backfill the missing v1.5.0 changelog
  • 9e0f31c release: v1.5.0 - add an exclude option for test discovery
  • 1241f7f release: v1.4.4 - drop the tsup-availability guard in prepack (#41)
  • See full diff in compare view

Updates typescript-eslint from 8.70.1 to 8.71.0

Release notes

Sourced from typescript-eslint's releases.

v8.71.0

8.71.0 (2026-09-28)

🚀 Features

  • eslint-plugin: [no-unsafe-enum-assignment] add rule (#12732)

🩹 Fixes

  • eslint-plugin: [switch-exhaustiveness-check] always sort literal cases in stable order (#12885)
  • eslint-plugin: [unbound-method] respect this: void on class properties (7fce9127d)
  • eslint-plugin: [no-unnecessary-type-assertion] specialize generic assertion report message (#12832)
  • eslint-plugin: [no-misused-promises] handle a return outside of any function (#12912)

❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from typescript-eslint's changelog.

8.71.0 (2026-09-28)

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

Commits

@cldmv-bot cldmv-bot Bot added the type: dependencies Relates to dependency updates, version bumps, or package management label Oct 2, 2026
Shinrai and others added 4 commits October 2, 2026 16:14
The Required PR Check mirror job was skipped on the `pull_request` run of
an in-repo feature PR, with a conditional name keeping the skipped check
off `✅ Required PR Check`. GitHub never evaluates a skipped job's
`name:`, so every in-repo PR showed the raw expression as a check name.

The job now uses `if: always()` and never skips, so its name is always
evaluated. On the in-repo PR path it lands on
`⏭️ Required PR Check (reported by the push run)` and passes as a no-op;
the push run still posts `✅ Required PR Check`. Every path that posts
the required name keeps `needs: ci`, so that check still only exists
once the full test matrix for the SHA has finished.

Synced from CLDMV/.github#351 (CLDMV/.github#350).
Bumps the minor group with 2 updates in the / directory: [@cldmv/vitest-runner](https://github.com/CLDMV/vitest-runner) and [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint).


Updates `@cldmv/vitest-runner` from 1.4.3 to 1.5.1
- [Release notes](https://github.com/CLDMV/vitest-runner/releases)
- [Commits](CLDMV/vitest-runner@v1.4.3...v1.5.1)

Updates `typescript-eslint` from 8.70.1 to 8.71.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.71.0/packages/typescript-eslint)

---
updated-dependencies:
- dependency-name: "@cldmv/vitest-runner"
  dependency-version: 1.5.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
- dependency-name: typescript-eslint
  dependency-version: 8.71.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title deps: bump the minor group with 2 updates deps: bump the minor group across 1 directory with 2 updates Oct 3, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/next/minor-25059ba4aa branch from 51e0a32 to 5fe45e9 Compare October 3, 2026 03:09
@Shinrai
Shinrai merged commit f128f02 into next Oct 3, 2026
27 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/next/minor-25059ba4aa branch October 3, 2026 18:12
cldmv-bot Bot added a commit that referenced this pull request Oct 5, 2026
# @cldmv/jsonv v1.1.4 Changelog

**Release Date**: October 2026
**Release Type**: Patch
**Branch**: `release/1.1.4`

---

## Overview

Version 1.1.4 fixes the CommonJS entry points. Until now `require("@cldmv/jsonv")`, and every `require("@cldmv/jsonv/<year>")`, returned a Promise of the ESM module rather than the API, so CommonJS code had to `await` it. `require()` now returns the same exports as `import`, synchronously, loaded through Node's `require(esm)`.

Existing `await require("@cldmv/jsonv")` code keeps working unchanged. Two cases do change and are covered in the upgrade notes below: code that chained `.then()` on the `require()` result, and CommonJS code on Node.js versions without `require(esm)`. The ESM API is untouched. The dev toolchain is also refreshed (`@cldmv/fix-headers` 2.2.0, `@cldmv/configs` 1.2.4, `@cldmv/vitest-runner` 1.5.1, `typescript-eslint` 8.71.0); none of it ships in the package.

---

## 🐛 Bug Fixes

### `require()` is a synchronous wrapper around the ESM build ([#80](#80))

The CommonJS build went through a generated `loader.cjs` that did `module.exports = (async () => await import("../index.mjs"))()`, so `require()` handed back a Promise. Every generated `.cjs` file is now a thin wrapper, `module.exports = require("<esm file>")`, so `require()` returns the same module namespace object as `import`:

```js
const { parse } = require("@cldmv/jsonv");
parse("{ a: 1 }"); // { a: 1 }

const jsonv2021 = require("@cldmv/jsonv/2021");
```

The rest of the CommonJS build was tidied along the way:

- The async `loader.cjs` is no longer generated, and `dist/cjs` is rebuilt from scratch on every build so a removed wrapper can't linger.
- `@cldmv/jsonv/year-resolver` now has a CommonJS wrapper. The `"./*"` export already pointed `require` at `dist/cjs/years/year-resolver.cjs`, but that file was never built, so `require("@cldmv/jsonv/year-resolver")` failed outright. `@cldmv/jsonv/loader` and the year modules are wrapped the same way.
- On Node.js without `require(esm)` (before 20.19.0, or 22.0–22.11), the wrappers throw an `ERR_REQUIRE_ESM` error whose message names the required Node.js versions and points to `import()`, instead of failing with a bare loader error.

---

## 🔧 CI & tooling

- New `tests/cjs/entry.test.cjs` (`node:test`), run by `npm test` and `npm run coverage` after Vitest through a new `test:cjs` script. It checks against the built `dist/` that `require()` of the entry and of a year module returns the same exports as `import`, and that the Node.js version check fires when `require(esm)` is unavailable.

---

## 📚 Documentation

- **NEW:** [docs/changelog/v1/v1.1.4.md](./v1.1.4.md) — this changelog.
- [docs/versioning-and-exports.md](https://github.com/CLDMV/jsonv/blob/master/docs/versioning-and-exports.md) — notes that `require()` is synchronous and states its Node.js requirement.
- README — restructured to the CLDMV README layout (badges, What's New, Installation with Node.js requirements, Documentation index, Links), with the changelog history backfilled for every earlier release under `docs/changelog/v1/`.

---

## 🔧 Dependencies

All development-only:

- `@cldmv/vitest-runner` 1.4.3 → 1.5.1 ([#77](#77))
- `typescript-eslint` 8.70.1 → 8.71.0 ([#77](#77))
- `@cldmv/fix-headers` `^2.1.1` → `^2.2.0`, resolved to 2.2.0. The range was first raised to `^2.1.4` ([#83](#83)) and then to `^2.2.0` ([#85](#85)). Version 2.1.4 no longer writes a JavaScript comment into JSON or Markdown files, processes every repeated `--input`, and never walks dependency folders such as `node_modules`. Version 2.2.0 changes `@Last modified by` only when a file's content was edited, so header-only rewrites keep the recorded editor.
- `@cldmv/configs` `^1.2.0` → `^1.2.4`, resolved to 1.2.4. The shared fix-headers config now sets `forceAuthorUpdate` and `forceLastModifiedAuthorUpdate` to false ([#85](#85)).
- No file headers were restamped: each fix-headers bump changed only `package.json` and the lockfile.

---

## Upgrade notes

- **`await require(...)` keeps working.** Awaiting a non-Promise returns it unchanged, so CommonJS code written against the old Promise-returning entry needs no change.
- **`.then()` on the `require()` result no longer works.** `require("@cldmv/jsonv").then((jsonv) => ...)` now throws `TypeError: ... .then is not a function`, because the result is the module itself. Use the result directly (`const jsonv = require("@cldmv/jsonv")`), or `await` it.
- **CommonJS needs Node.js ^20.19.0 or >=22.12.0.** On older Node.js, where `await require("@cldmv/jsonv")` used to resolve through the async loader, `require()` now throws `ERR_REQUIRE_ESM` with a message pointing to `import()`. Load the package with `await import("@cldmv/jsonv")` there. The `engines` field (`>=18.0.0`) and ESM `import` support are unchanged.



<details>
<summary>👥 Contributors</summary>

- @Shinrai

</details>

---

<!-- coverage-start -->

![coverage](https://img.shields.io/badge/coverage-98.7%25-brightgreen?style=for-the-badge&logo=vitest&logoColor=white)

| Metric | Coverage |
|--------|----------|
| Statements | 98.7% |
| Branches   | 97.3% |
| Functions  | 100.0% |
| Lines      | 98.8% |

*Avg: **98.7%** · `640792e` · Node lts/**

<!-- coverage-end -->

<!-- co-authors -->

Co-authored-by: Shinrai <Shinrai@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: dependencies Relates to dependency updates, version bumps, or package management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant