build(deps): bump github.com/google/flatbuffers from 22.10.26+incompatible to 23.1.4+incompatible

Закрыто lebedev.k.m запросил слияние dependabot/go_modules/github.com/google/flatbuffers-23.1.4incompatible в master

Created by: dependabot[bot]

Bumps github.com/google/flatbuffers from 22.10.26+incompatible to 23.1.4+incompatible.

Release notes

Sourced from github.com/google/flatbuffers's releases.

v23.1.4

Changelog

Happy New Year!

What's Changed

New Contributors

Full Changelog: https://github.com/google/flatbuffers/compare/v22.12.06...v23.1.4

v22.12.06

What's Changed

... (truncated)

Changelog

Sourced from github.com/google/flatbuffers's changelog.

Flatbuffers Change Log

All major or breaking changes will be documented in this file, as well as any new features that should be highlighted. Minor fixes or improvements are not necessarily listed.

23.1.4 (Jan 4 2023)

  • Major release! Just kidding, we are continuing the versioning scheme of using a date to signify releases. This results in the first release of the new year to bump the tradition major version field.

  • Go minimum version is now 1.19 (#7720) with the addition of Go modules.

  • Added CI support for Big Endian regression testing (#7707).

  • Fixed getFullyQualifiedName in typescript to return name delimited by '.' instead of '_' (#7730).

  • Fixed the versioning scheme to not include leading zeros which are not consistently handled by every package manager. Only the last release (12.12.06) should have suffered from this.

22.12.06 (Dec 06 2022)

  • Bug fixing release, no major changes.

22.10.25 (Oct 25 2022)

  • Added Nim language support with generator and runtime libraries (#7534).

22.9.29 (Sept 29 2022)

  • Rust soundness fixes to avoid the crate from bing labelled unsafe (#7518).

22.9.24 (Sept 24 2022)

  • 20 Major releases in a row? Nope, we switched to a new versioning scheme that is based on date.

  • Python supports fixed size arrays now (#7529).

  • Behavior change in how C++ object API uses UnPackTo. The original intent of this was to reduce allocations by reusing an existing object to pack data into. At some point, this logic started to merge the states of the two objects instead of clearing the state of the packee. This change goes back to the original intention, the packed object is cleared when getting data packed into it (#7527).

... (truncated)

Commits

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)