@ogma/platform-ws@3.0.0

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/platform-tcp@3.0.0

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/platform-socket.io@3.0.0

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

Patch Changes

• Updated dependencies [5e51fdc]
  • @ogma/nestjs-module@3.0.0

@ogma/platform-redis@3.0.0

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/platform-rabbitmq@3.0.0

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/platform-nats@3.0.0

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/platform-mqtt@3.0.0

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/platform-kafka@3.0.0

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/platform-grpc@3.0.0

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/platform-graphql@3.0.0

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.