fabric-samples icon indicating copy to clipboard operation
fabric-samples copied to clipboard
verified publisher icon hyperledger

Bump the go_modules group across 3 directories with 1 update

Open dependabot[bot] opened this issue 2 months ago • 1 comments

Bumps the go_modules group with 1 update in the /token-sdk/auditor directory: github.com/consensys/gnark-crypto. Bumps the go_modules group with 1 update in the /token-sdk/issuer directory: github.com/consensys/gnark-crypto. Bumps the go_modules group with 1 update in the /token-sdk/owner directory: github.com/consensys/gnark-crypto.

Updates github.com/consensys/gnark-crypto from 0.12.1 to 0.18.1

Release notes

Sourced from github.com/consensys/gnark-crypto's releases.

v0.18.1

Full Changelog: https://github.com/Consensys/gnark-crypto/compare/v0.18.0...v0.18.1

v0.18.0

What's Changed

New Contributors

Full Changelog: https://github.com/Consensys/gnark-crypto/compare/v0.17.0...v0.18.0

v0.17.0

What's Changed

New Contributors

... (truncated)

Changelog

Sourced from github.com/consensys/gnark-crypto's changelog.

[v0.18.1] - 2025-10-23

Perf

  • limit memory allocation during Vector deserialization (#759)

[v0.18.0] - 2025-06-09

Build

  • deps: bump golang.org/x/crypto from 0.33.0 to 0.35.0 (#677)

Chore

  • remove unused benchmark script (#675)

Docs

  • replace outdated link to article (#690)

Experiment

  • vortex on koalabear (#645)

Feat

  • remove dependency on internal package in ecc.go (#693)
  • make <31 bit field generated using uint32 (#676)

Fix

  • remove unimplemented path from fft ext
  • Eisenstein Half-GCD convergence (#680)

Perf

  • adds avx512 poseidon2 for small fields (#665)
  • remove useless copies in e4 mul by elem (#667)
  • disable cobra bit reverse for small fields (#662)

Refactor

  • hash to curve (#674)

[v0.17.0] - 2025-03-11

Chore

  • remove useless github workflow
  • generify poseidon2 parameters for other curves/fr (#636)
  • add auto close PR workflow (#638)

Feat

  • baby-bear and koala-bear extensions of degree 4 (#643)
  • poseidon2 for koala-bear, baby-bear and goldilocks (#629)
  • add sis avx512 and fft avx512 for koalabear (#622)
  • add Grumpkin elliptic curve (2-cycle with BN254) (#625)
  • Poseidon2 Hash Instantiation for BLS12-377 (#623)

... (truncated)

Commits

Updates github.com/consensys/gnark-crypto from 0.12.1 to 0.18.1

Release notes

Sourced from github.com/consensys/gnark-crypto's releases.

v0.18.1

Full Changelog: https://github.com/Consensys/gnark-crypto/compare/v0.18.0...v0.18.1

v0.18.0

What's Changed

New Contributors

Full Changelog: https://github.com/Consensys/gnark-crypto/compare/v0.17.0...v0.18.0

v0.17.0

What's Changed

New Contributors

... (truncated)

Changelog

Sourced from github.com/consensys/gnark-crypto's changelog.

[v0.18.1] - 2025-10-23

Perf

  • limit memory allocation during Vector deserialization (#759)

[v0.18.0] - 2025-06-09

Build

  • deps: bump golang.org/x/crypto from 0.33.0 to 0.35.0 (#677)

Chore

  • remove unused benchmark script (#675)

Docs

  • replace outdated link to article (#690)

Experiment

  • vortex on koalabear (#645)

Feat

  • remove dependency on internal package in ecc.go (#693)
  • make <31 bit field generated using uint32 (#676)

Fix

  • remove unimplemented path from fft ext
  • Eisenstein Half-GCD convergence (#680)

Perf

  • adds avx512 poseidon2 for small fields (#665)
  • remove useless copies in e4 mul by elem (#667)
  • disable cobra bit reverse for small fields (#662)

Refactor

  • hash to curve (#674)

[v0.17.0] - 2025-03-11

Chore

  • remove useless github workflow
  • generify poseidon2 parameters for other curves/fr (#636)
  • add auto close PR workflow (#638)

Feat

  • baby-bear and koala-bear extensions of degree 4 (#643)
  • poseidon2 for koala-bear, baby-bear and goldilocks (#629)
  • add sis avx512 and fft avx512 for koalabear (#622)
  • add Grumpkin elliptic curve (2-cycle with BN254) (#625)
  • Poseidon2 Hash Instantiation for BLS12-377 (#623)

... (truncated)

Commits

Updates github.com/consensys/gnark-crypto from 0.12.1 to 0.18.1

Release notes

Sourced from github.com/consensys/gnark-crypto's releases.

v0.18.1

Full Changelog: https://github.com/Consensys/gnark-crypto/compare/v0.18.0...v0.18.1

v0.18.0

What's Changed

New Contributors

Full Changelog: https://github.com/Consensys/gnark-crypto/compare/v0.17.0...v0.18.0

v0.17.0

What's Changed

New Contributors

... (truncated)

Changelog

Sourced from github.com/consensys/gnark-crypto's changelog.

[v0.18.1] - 2025-10-23

Perf

  • limit memory allocation during Vector deserialization (#759)

[v0.18.0] - 2025-06-09

Build

  • deps: bump golang.org/x/crypto from 0.33.0 to 0.35.0 (#677)

Chore

  • remove unused benchmark script (#675)

Docs

  • replace outdated link to article (#690)

Experiment

  • vortex on koalabear (#645)

Feat

  • remove dependency on internal package in ecc.go (#693)
  • make <31 bit field generated using uint32 (#676)

Fix

  • remove unimplemented path from fft ext
  • Eisenstein Half-GCD convergence (#680)

Perf

  • adds avx512 poseidon2 for small fields (#665)
  • remove useless copies in e4 mul by elem (#667)
  • disable cobra bit reverse for small fields (#662)

Refactor

  • hash to curve (#674)

[v0.17.0] - 2025-03-11

Chore

  • remove useless github workflow
  • generify poseidon2 parameters for other curves/fr (#636)
  • add auto close PR workflow (#638)

Feat

  • baby-bear and koala-bear extensions of degree 4 (#643)
  • poseidon2 for koala-bear, baby-bear and goldilocks (#629)
  • add sis avx512 and fft avx512 for koalabear (#622)
  • add Grumpkin elliptic curve (2-cycle with BN254) (#625)
  • Poseidon2 Hash Instantiation for BLS12-377 (#623)

... (truncated)

Commits

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 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 You can disable automated security fix PRs for this repo from the Security Alerts page.

dependabot[bot] avatar Oct 30 '25 17:10 dependabot[bot]

@dependabot recreate

bestbeforetoday avatar Oct 31 '25 11:10 bestbeforetoday

@hyperledger/fabric-samples-maintainers The ‎token-sdk sample being updated by this dependabot pull request is not covered by any of the automated build checks. This makes me nervous about merging changes to this sample. Ideally this sample would be included in the automated build but I don't see anyone with time or motivation to do that. Given there is no build coverage, I wonder if we should:

  1. Just go ahead and merge dependency changes like this and wait for users to tell us if the token-sdk sample gets broken;
  2. Remove the sample;
  3. Something else... (suggestions welcome).

What do you think?

bestbeforetoday avatar Nov 06 '25 17:11 bestbeforetoday

@hyperledger/fabric-samples-maintainers @bestbeforetoday Thank you for raising this point.

Here are my thoughts:

  • As far as I understand, token-sdk itself is a Labs project. Given the limited resources and time available, I think our focus should remain on maintaining samples related to the official (non-Labs) Fabric projects. There are also other chaincode-based token samples that already demonstrate how Fabric can be used for token-related use cases.
  • So, I’d be okay if we decided to remove this sample for now. Should user demand arise in the future, or if contributors express willingness to contribute to the token-sdk sample (including adding automated build coverage), it could be revived at any time.
  • That said, I’d also be fine with the “just go ahead and merge dependency changes and wait for users to report issues” option if others think that’s sufficient.

satota2 avatar Nov 07 '25 01:11 satota2