standard-log@13.3.0

Minor Changes

• b95eeeb: Bump iso-error from ^6.0.5 to ^7.0.0.

  iso-error@7.0.0's major came from raising engines.node to >= 20 (needed for
  type-plus@8's unpartial@^1.0.7 dependency) and pinning type-plus as a
  devDependency — not from an API change. IsoError and ModuleError, the types
  standard-log re-exports from iso-error in errors.ts (and which leak into the
  emitted .d.ts), are unchanged in shape between 6.0.5 and 7.0.0, so this ships
  as minor rather than major here, matching the same reasoning used for the
  identical bump in cyberuni/assertron#359.

  This lets consumers of standard-log drop a duplicate iso-error@6 from their
  dependency tree now that iso-error@7 is the only version other parts of the graph
  (e.g. @unional/fixture) resolve.

standard-log@13.2.0

Minor Changes

• 6b69b99: Widen @just-func/types from ^0.5.0 to ^0.6.0, and pin type-plus to 8.0.0-beta.10, exactly.

  The unblock: @just-func/types. The published @just-func/types@0.5.1 still depends
  on type-plus@^5.0.0, so every consumer of standard-log dragged type-plus@5.6.0 into
  its tree regardless of what else was pinned. @just-func/types@0.6.0 is already on
  type-plus@8.0.0-beta.10, but ^0.5.0 does not admit a 0.x minor bump, so the widen to
  ^0.6.0 is required to let it resolve. This removes a transitive type-plus@5.6.0 from
  every consumer's tree — that is the user-visible benefit of this release.

  This is not a major bump: standard-log@13.1.0, the last published version, already
  declared type-plus: ^8.0.0-beta.10, so the typescript >= 5.6.0 peer it carries already
  reached consumers in that release. Tightening the range to an exact version does not add
  a new peer requirement, and building the package confirms no type-plus types leak into
  the emitted .d.ts. The @just-func/types widening does change the resolved runtime
  dependency tree for consumers (a minor-worthy change on its own), so this release is a
  minor overall.

  Why pin instead of caret-range type-plus. ^8.0.0-beta.10 resolves to
  >=8.0.0-beta.10 <9.0.0-0, which admits every later 8.0.0 prerelease plus 8.0.0 and
  8.1.0. 8 is a prerelease line where breaking changes land between betas — beta.10 to
  beta.11 changed Equal's signature and removed isType.f. An exact version makes each
  bump a reviewable PR rather than something a lockfile refresh can do silently. Move back
  to a caret once 8.0.0 is stable.

  No source changes were needed for either move: this package's type-plus and
  @just-func/types usage is unaffected by the 7 -> 8 and 0.5 -> 0.6 type surface changes.

standard-log@13.1.0

Minor Changes

• bd1b2e8: Move type-plus from ^7.0.0 to ^8.0.0-beta.10.

  type-plus 7 depends on tersify ^3, and because type-plus is a runtime dependency of
  standard-log, that pulled tersify 3.x into every downstream consumer's tree — including
  @just-web/log, which ends up with two majors of tersify installed side by side.
  type-plus 8 depends on tersify ^4, so this deduplicates that for consumers.

  The range is a caret on the beta so it resolves forward to 8.0.0 once that ships.

  Bumped as a minor rather than a patch: no public type or runtime API of standard-log
  changes (the built .d.ts files reference no type-plus types, and all four packages
  build, typecheck, and test unchanged), but consumers do get a different major of a
  runtime dependency, which is more than a bug fix.

standard-log-syslog@13.3.0

Version Packages (#463)

This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.

# Releases
## standard-log@13.3.0

### Minor Changes

- b95eeeb: Bump `iso-error` from `^6.0.5` to `^7.0.0`.

`iso-error@7.0.0`'s major came from raising `engines.node` to `>= 20`
(needed for
`type-plus@8`'s `unpartial@^1.0.7` dependency) and pinning `type-plus`
as a
devDependency — not from an API change. `IsoError` and `ModuleError`,
the types
`standard-log` re-exports from `iso-error` in `errors.ts` (and which
leak into the
emitted `.d.ts`), are unchanged in shape between `6.0.5` and `7.0.0`, so
this ships
as `minor` rather than `major` here, matching the same reasoning used
for the
  identical bump in `cyberuni/assertron#359`.

This lets consumers of `standard-log` drop a duplicate `iso-error@6`
from their
dependency tree now that `iso-error@7` is the only version other parts
of the graph
  (e.g. `@unional/fixture`) resolve.
## standard-log-color@13.3.0

## standard-log-remote@13.3.0

## standard-log-syslog@13.3.0

standard-log-syslog@13.2.0

Version Packages (#461)

This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.

# Releases
## standard-log@13.2.0

### Minor Changes

- 6b69b99: Widen `@just-func/types` from `^0.5.0` to `^0.6.0`, and pin
`type-plus` to `8.0.0-beta.10`, exactly.

**The unblock: `@just-func/types`.** The published
`@just-func/types@0.5.1` still depends
on `type-plus@^5.0.0`, so every consumer of `standard-log` dragged
`type-plus@5.6.0` into
its tree regardless of what else was pinned. `@just-func/types@0.6.0` is
already on
`type-plus@8.0.0-beta.10`, but `^0.5.0` does not admit a `0.x` minor
bump, so the widen to
`^0.6.0` is required to let it resolve. This removes a transitive
`type-plus@5.6.0` from
every consumer's tree — that is the user-visible benefit of this
release.

This is not a major bump: `standard-log@13.1.0`, the last published
version, already
declared `type-plus: ^8.0.0-beta.10`, so the `typescript >= 5.6.0` peer
it carries already
reached consumers in that release. Tightening the range to an exact
version does not add
a new peer requirement, and building the package confirms no `type-plus`
types leak into
the emitted `.d.ts`. The `@just-func/types` widening does change the
resolved runtime
dependency tree for consumers (a `minor`-worthy change on its own), so
this release is a
  `minor` overall.

**Why pin instead of caret-range `type-plus`.** `^8.0.0-beta.10`
resolves to
`>=8.0.0-beta.10 <9.0.0-0`, which admits every later 8.0.0 prerelease
plus `8.0.0` and
`8.1.0`. 8 is a prerelease line where breaking changes land between
betas — beta.10 to
beta.11 changed `Equal`'s signature and removed `isType.f`. An exact
version makes each
bump a reviewable PR rather than something a lockfile refresh can do
silently. Move back
  to a caret once 8.0.0 is stable.

No source changes were needed for either move: this package's
`type-plus` and
`@just-func/types` usage is unaffected by the 7 -> 8 and 0.5 -> 0.6 type
surface changes.
## standard-log-color@13.2.0

## standard-log-remote@13.2.0

## standard-log-syslog@13.2.0

standard-log-syslog@13.1.0

Version Packages (#459)

This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.

# Releases
## standard-log@13.1.0

### Minor Changes

- bd1b2e8: Move `type-plus` from `^7.0.0` to `^8.0.0-beta.10`.

`type-plus` 7 depends on `tersify` ^3, and because `type-plus` is a
runtime dependency of
`standard-log`, that pulled `tersify` 3.x into every downstream
consumer's tree — including
`@just-web/log`, which ends up with two majors of `tersify` installed
side by side.
`type-plus` 8 depends on `tersify` ^4, so this deduplicates that for
consumers.

The range is a caret on the beta so it resolves forward to `8.0.0` once
that ships.

Bumped as a minor rather than a patch: no public type or runtime API of
`standard-log`
changes (the built `.d.ts` files reference no `type-plus` types, and all
four packages
build, typecheck, and test unchanged), but consumers do get a different
major of a
  runtime dependency, which is more than a bug fix.
## standard-log-color@13.1.0

## standard-log-remote@13.1.0

## standard-log-syslog@13.1.0

standard-log-remote@13.3.0

Version Packages (#463)

This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.

# Releases
## standard-log@13.3.0

### Minor Changes

- b95eeeb: Bump `iso-error` from `^6.0.5` to `^7.0.0`.

`iso-error@7.0.0`'s major came from raising `engines.node` to `>= 20`
(needed for
`type-plus@8`'s `unpartial@^1.0.7` dependency) and pinning `type-plus`
as a
devDependency — not from an API change. `IsoError` and `ModuleError`,
the types
`standard-log` re-exports from `iso-error` in `errors.ts` (and which
leak into the
emitted `.d.ts`), are unchanged in shape between `6.0.5` and `7.0.0`, so
this ships
as `minor` rather than `major` here, matching the same reasoning used
for the
  identical bump in `cyberuni/assertron#359`.

This lets consumers of `standard-log` drop a duplicate `iso-error@6`
from their
dependency tree now that `iso-error@7` is the only version other parts
of the graph
  (e.g. `@unional/fixture`) resolve.
## standard-log-color@13.3.0

## standard-log-remote@13.3.0

## standard-log-syslog@13.3.0

standard-log-remote@13.2.0

Version Packages (#461)

This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.

# Releases
## standard-log@13.2.0

### Minor Changes

- 6b69b99: Widen `@just-func/types` from `^0.5.0` to `^0.6.0`, and pin
`type-plus` to `8.0.0-beta.10`, exactly.

**The unblock: `@just-func/types`.** The published
`@just-func/types@0.5.1` still depends
on `type-plus@^5.0.0`, so every consumer of `standard-log` dragged
`type-plus@5.6.0` into
its tree regardless of what else was pinned. `@just-func/types@0.6.0` is
already on
`type-plus@8.0.0-beta.10`, but `^0.5.0` does not admit a `0.x` minor
bump, so the widen to
`^0.6.0` is required to let it resolve. This removes a transitive
`type-plus@5.6.0` from
every consumer's tree — that is the user-visible benefit of this
release.

This is not a major bump: `standard-log@13.1.0`, the last published
version, already
declared `type-plus: ^8.0.0-beta.10`, so the `typescript >= 5.6.0` peer
it carries already
reached consumers in that release. Tightening the range to an exact
version does not add
a new peer requirement, and building the package confirms no `type-plus`
types leak into
the emitted `.d.ts`. The `@just-func/types` widening does change the
resolved runtime
dependency tree for consumers (a `minor`-worthy change on its own), so
this release is a
  `minor` overall.

**Why pin instead of caret-range `type-plus`.** `^8.0.0-beta.10`
resolves to
`>=8.0.0-beta.10 <9.0.0-0`, which admits every later 8.0.0 prerelease
plus `8.0.0` and
`8.1.0`. 8 is a prerelease line where breaking changes land between
betas — beta.10 to
beta.11 changed `Equal`'s signature and removed `isType.f`. An exact
version makes each
bump a reviewable PR rather than something a lockfile refresh can do
silently. Move back
  to a caret once 8.0.0 is stable.

No source changes were needed for either move: this package's
`type-plus` and
`@just-func/types` usage is unaffected by the 7 -> 8 and 0.5 -> 0.6 type
surface changes.
## standard-log-color@13.2.0

## standard-log-remote@13.2.0

## standard-log-syslog@13.2.0

standard-log-remote@13.1.0

Version Packages (#459)

This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.

# Releases
## standard-log@13.1.0

### Minor Changes

- bd1b2e8: Move `type-plus` from `^7.0.0` to `^8.0.0-beta.10`.

`type-plus` 7 depends on `tersify` ^3, and because `type-plus` is a
runtime dependency of
`standard-log`, that pulled `tersify` 3.x into every downstream
consumer's tree — including
`@just-web/log`, which ends up with two majors of `tersify` installed
side by side.
`type-plus` 8 depends on `tersify` ^4, so this deduplicates that for
consumers.

The range is a caret on the beta so it resolves forward to `8.0.0` once
that ships.

Bumped as a minor rather than a patch: no public type or runtime API of
`standard-log`
changes (the built `.d.ts` files reference no `type-plus` types, and all
four packages
build, typecheck, and test unchanged), but consumers do get a different
major of a
  runtime dependency, which is more than a bug fix.
## standard-log-color@13.1.0

## standard-log-remote@13.1.0

## standard-log-syslog@13.1.0

standard-log-color@13.3.0

Version Packages (#463)

This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.

# Releases
## standard-log@13.3.0

### Minor Changes

- b95eeeb: Bump `iso-error` from `^6.0.5` to `^7.0.0`.

`iso-error@7.0.0`'s major came from raising `engines.node` to `>= 20`
(needed for
`type-plus@8`'s `unpartial@^1.0.7` dependency) and pinning `type-plus`
as a
devDependency — not from an API change. `IsoError` and `ModuleError`,
the types
`standard-log` re-exports from `iso-error` in `errors.ts` (and which
leak into the
emitted `.d.ts`), are unchanged in shape between `6.0.5` and `7.0.0`, so
this ships
as `minor` rather than `major` here, matching the same reasoning used
for the
  identical bump in `cyberuni/assertron#359`.

This lets consumers of `standard-log` drop a duplicate `iso-error@6`
from their
dependency tree now that `iso-error@7` is the only version other parts
of the graph
  (e.g. `@unional/fixture`) resolve.
## standard-log-color@13.3.0

## standard-log-remote@13.3.0

## standard-log-syslog@13.3.0