Jiyoon Koo
Jiyoon Koo
@LiranCohen ah! i found the ci run where it failed. i just had to click 5 levels deep to find it https://github.com/TBD54566975/web5-js/actions/runs/8516766403/job/23326301339
maybe related - node-sdk-reports also fails intermittently https://github.com/TBD54566975/web5-js/actions/runs/8541288382/job/23400248626 and https://github.com/TBD54566975/web5-js/actions/runs/8485265479/job/23249737612
how do we feel about only scoping the 3 approvals to spec / api changes, and not test vector changes? currently the flow we generally all follow is: 1. PR...
looks like security audit is failing @nitro-neal - something about mysql? can you look into this and either bump or remove the dep
can you explain how fixing the vuln in a different repo would also address it here? is it somehow linked?
have you tried using the [GetMany](https://github.com/tidwall/gjson/blob/master/gjson.go#L2335-L2344) function? looks like it should do what you want.
just want to clarify - is this work slated for 1.0?
closing as this became stale, and merging this would break the CI. select credential method must be updated per https://github.com/TBD54566975/web5-js/issues/512 for this submodule commit bump to pass.
@peacekeeper just FYI, this is giving us 404 today: https://repo.maven.apache.org/maven2/com/danubetech/verifiable-credentials-java/1.6.0/verifiable-credentials-java-1.6.0.pom would you consider publishing to maven central?
notes out of tbdex discussion - `region` means `thisOfferingCanSupportCustomersOriginatingIn` - consider coming up with a clearer name that meets this definition - make `region` top level required, and `payin.region` and...