Skip to content

chore(deps): bump the npm-major group across 1 directory with 5 updates - #17

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-major-58ca2cc3ca
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-major-58ca2cc3ca

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor

Bumps the npm-major group with 5 updates in the / directory:

Package From To
@xfcfam/xf 0.2.0 1.2.0
typescript 6.0.3 7.0.2
@changesets/cli 2.31.0 3.0.1
@types/node 25.9.3 26.4.1
vitest 4.1.8 5.0.0

Updates @xfcfam/xf from 0.2.0 to 1.2.0

Release notes

Sourced from @​xfcfam/xf's releases.

@​xfcfam/xf-client-http@​1.2.0

No release notes provided.

@​xfcfam/xf-client@​1.2.0

No release notes provided.

@​xfcfam/xf-fs@​1.2.0

No release notes provided.

@​xfcfam/xf-kv-memcached@​1.2.0

No release notes provided.

@​xfcfam/xf-kv-redis@​1.2.0

No release notes provided.

@​xfcfam/xf-kv@​1.2.0

No release notes provided.

@​xfcfam/xf-logger-file@​1.2.0

No release notes provided.

@​xfcfam/xf-logger@​1.2.0

No release notes provided.

@​xfcfam/xf-react-view@​1.2.0

No release notes provided.

@​xfcfam/xf-reactnative-fs@​1.2.0

No release notes provided.

@​xfcfam/xf-rest@​1.2.0

No release notes provided.

@​xfcfam/xf-server-http@​1.2.0

No release notes provided.

@​xfcfam/xf-server@​1.2.0

No release notes provided.

@​xfcfam/xf-sql-postgres@​1.2.0

Minor Changes

  • 46d209f: Add camelToSnake to DatabaseOptions and PostgresOptions

    Opt-in flag (default false) that bridges camelCase implementer code and a snake_case schema — the usual Postgres convention — in both directions, by installing Kysely's CamelCasePlugin.

    Going in, every identifier Kysely puts in a query is written snake_case: columns in values(...), set(...), where(...), select(...) and

... (truncated)

Changelog

Sourced from @​xfcfam/xf's changelog.

1.2.0

1.1.0

Minor Changes

  • ef38870: Add ConnectableRepository, a latched connection lifecycle for the Access Layer, and adopt it in xf-sql's DatabaseRepository.

    XF bootstraps downwards — R.init() finishes before B.init() starts — so a Repository always connects before any Business exists to hear about it. Subscribing to a plain connect event from B.init() therefore registers a callback for something that already happened: it never runs, nothing throws, and the state it was meant to populate stays empty. The bug is in the ordering, which is invisible at the call site.

    ConnectableRepository treats connection state as a latch rather than an event: onConnect(listener) fires immediately when the component is already connected, and again on every reconnect. Also provides onDisconnect, isConnected(), and idempotent markConnected() / markDisconnected() for subclasses. Listener failures are isolated and routed to the overridable onListenerError hook.

    DatabaseRepository now extends it and marks the transitions around its existing onConnected / onDisconnected subclass hooks, which keep their current meaning and firing order. No breaking change: subclasses that override the hooks are unaffected, and onConnect / isConnected are additive.

1.0.0

Major Changes

  • 80407e6: Adopt lockstep (fixed) versioning across the @xfcfam/* family and level the entire set to 1.0.0.

    From this release every published @xfcfam/* package shares a single version and bumps together, so any given version number identifies a mutually-compatible set. This stabilises the public API at 1.0 and removes the 0.x peer-range cascade — at ^1, a minor bump no longer forces a major bump on dependants. The internal grpc / tcp / udp sketches stay unversioned (0.0.0, private) until they graduate into the family.

0.3.0

Minor Changes

  • Broaden the observable/scheduled Business generalizations with a small, backward-compatible surface.

    • ObservableBusiness / ObservableScheduleBusiness: add an optional runOnObserve flag on observe(observer, runOnObserve?) that fires the observer immediately with the current state, and a notify(data?) overload that sets the state before fanning out. Observer callbacks are now isolated — a throwing observer no longer prevents the others from running. State stays protected — components that want to expose it add their own accessor over it (the generalization does not publish it by default).
    • ScheduleBusiness: interval(ms, runImmediately?) can run one tick up front; add an onError(error) hook (default swallows) so a single failing tick never aborts the schedule.

    ObservableScheduleBusiness is now a clean composition of the two concerns: it no longer notifies observers on every tick. Scheduling and observation are orthogonal — a tick is not a state change — so observers are notified only when the component publishes a new state via notify(...), exactly like ObservableBusiness. (Behavioural change vs the previous auto-notify-per-tick; subclasses now call notify from run when there is something new.)

    Existing call sites (notify(), observe(observer)) are unchanged.

Commits
  • 002f7e9 chore(release): version packages (#61)
  • 0743cac chore(release): version packages (#56)
  • ef38870 feat(xf): ConnectableRepository — latched connection lifecycle (#55)
  • 2bce348 chore(release): version packages (#50)
  • f76cb96 feat(xf): broaden observable/scheduled Business surface; version packages (xf...
  • See full diff in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​xfcfam/xf since your current version.


Updates typescript from 6.0.3 to 7.0.2

Release notes

Sourced from typescript's releases.

TypeScript 7.0.2

https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/

This tag was originally released at: https://github.com/microsoft/typescript-go/releases/tag/typescript%2Fv7.0.2

Commits
  • 1e4744d Merge branch 'main' into ts7-release
  • a5a219cmicrosoft/typescript-go#4558
  • ecfe30d Update status localization
  • 5de25b5 Hide executable name in TypeScript status
  • d7ce74a Show bundled TypeScript version for packaged servers
  • 29be66a Correct TS 7 release version to 7.0.2
  • ed2bd1b Merge branch 'main' into ts7-release
  • 8873075 Bump the github-actions group across 1 directory with 3 updates (microsoft/ty...
  • 9427131 Set up stable / nightly extension split, other prep (microsoft/typescript-go#...
  • d4eaca5microsoft/typescript-go#4549
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.


Updates @changesets/cli from 2.31.0 to 3.0.1

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​3.0.1

Patch Changes

@​changesets/cli@​3.0.0

Major Changes

  • #2128 7113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

  • #2074 3599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

  • #1860 92b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

    This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

  • #1482 df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

  • #1994 062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

  • #2190 96b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

    This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

  • #2145 f5887ff Thanks @​Andarist! - Removed Yarn Classic support

  • #2097 8c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

  • #1879 c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

  • #1655 db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

  • #1651 e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

  • #2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

  • #1961 07278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

  • #1482 df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

  • #1652 a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

  • #2186 3910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

  • #1879 c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

    This means the CLI flows will have minor changes, but they are largely the same.

... (truncated)

Changelog

Sourced from @​changesets/cli's changelog.

3.0.1

Patch Changes

3.0.0

Major Changes

  • #2128 7113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

  • #2074 3599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

  • #1860 92b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

    This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

  • #1482 df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

  • #1994 062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

  • #2190 96b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

    This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

  • #2145 f5887ff Thanks @​Andarist! - Removed Yarn Classic support

  • #2097 8c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

  • #1879 c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

  • #1655 db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

  • #1651 e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

  • #2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

  • #1961 07278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

  • #1482 df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

  • #1652 a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

  • #2186 3910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

  • #1879 c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

... (truncated)

Commits

Updates @types/node from 25.9.3 to 26.4.1

Commits

Updates vitest from 4.1.8 to 5.0.0

Release notes

Sourced from vitest's releases.

v5.0.0

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes

... (truncated)

Commits
  • f441c6f chore: release v5.0.0 (#11130)
  • d46a747 fix: treat test.describe as a suite during static collection (#11128)
  • 584cf30 fix: add a warning if inline project has duplicate plugins due to unexpected ...
  • f08ce4b fix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)
  • 897f51f chore: release v5.0.0-rc.4 (#11107)
  • 1339b06 chore(deps): update all non-major dependencies (#11104)
  • 51e9494 feat!: parse files statically in vitest list by default (#11088)
  • 2122ffd fix: propagate --maxWorkers to projects (#11102)
  • dc10f5f fix(browser): report the action error when a task times out (#11101)
  • d4fe198 feat: promote clearCache out of experimental (#11086)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the npm-major group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@xfcfam/xf](https://github.com/xfcfam/lib-npm/tree/HEAD/packages/xf) | `0.2.0` | `1.2.0` |
| [typescript](https://github.com/microsoft/TypeScript) | `6.0.3` | `7.0.2` |
| [@changesets/cli](https://github.com/changesets/changesets/tree/HEAD/packages/cli) | `2.31.0` | `3.0.1` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `25.9.3` | `26.4.1` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `4.1.8` | `5.0.0` |



Updates `@xfcfam/xf` from 0.2.0 to 1.2.0
- [Release notes](https://github.com/xfcfam/lib-npm/releases)
- [Changelog](https://github.com/xfcfam/lib-npm/blob/main/packages/xf/CHANGELOG.md)
- [Commits](https://github.com/xfcfam/lib-npm/commits/@xfcfam/xf@1.2.0/packages/xf)

Updates `typescript` from 6.0.3 to 7.0.2
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Commits](microsoft/TypeScript@v6.0.3...v7.0.2)

Updates `@changesets/cli` from 2.31.0 to 3.0.1
- [Release notes](https://github.com/changesets/changesets/releases)
- [Changelog](https://github.com/changesets/changesets/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/changesets/changesets/commits/@changesets/cli@3.0.1/packages/cli)

Updates `@types/node` from 25.9.3 to 26.4.1
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `vitest` from 4.1.8 to 5.0.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/vitest)

---
updated-dependencies:
- dependency-name: "@xfcfam/xf"
  dependency-version: 1.2.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: npm-major
- dependency-name: typescript
  dependency-version: 7.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: npm-major
- dependency-name: "@changesets/cli"
  dependency-version: 3.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-major
- dependency-name: "@types/node"
  dependency-version: 26.4.1
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-major
- dependency-name: vitest
  dependency-version: 5.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: npm. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot added the dependencies Pull requests that update dependencies label Sep 7, 2026
@dependabot
dependabot Bot requested a review from isramatrix as a code owner September 7, 2026 02:45
@dependabot dependabot Bot added the dependencies Pull requests that update dependencies label Sep 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants