Closed hacdias closed 1 year ago
Suggested version: v0.0.6
Changes in go.mod
file(s):
diff --git a/go.mod b/go.mod
index aa4d440..b71c615 100644
--- a/go.mod
+++ b/go.mod
@@ -8,4 +8,24 @@ require (
github.com/whyrusleeping/chunker v0.0.0-20181014151217-fe64bd25879f
)
-go 1.12
+require (
+ github.com/gogo/protobuf v1.2.1 // indirect
+ github.com/gxed/hashland/keccakpg v0.0.1 // indirect
+ github.com/gxed/hashland/murmur3 v0.0.1 // indirect
+ github.com/ipfs/go-cid v0.0.1 // indirect
+ github.com/mattn/go-colorable v0.1.1 // indirect
+ github.com/mattn/go-isatty v0.0.5 // indirect
+ github.com/minio/blake2b-simd v0.0.0-20160723061019-3f5f724cb5b1 // indirect
+ github.com/minio/sha256-simd v0.0.0-20190131020904-2d45a736cd16 // indirect
+ github.com/mr-tron/base58 v1.1.0 // indirect
+ github.com/multiformats/go-base32 v0.0.3 // indirect
+ github.com/multiformats/go-multibase v0.0.1 // indirect
+ github.com/multiformats/go-multihash v0.0.1 // indirect
+ github.com/opentracing/opentracing-go v1.0.2 // indirect
+ github.com/whyrusleeping/go-logging v0.0.0-20170515211332-0457bb6b88fc // indirect
+ golang.org/x/crypto v0.0.0-20190211182817-74369b46fc67 // indirect
+ golang.org/x/net v0.0.0-20190227160552-c95aed5357e7 // indirect
+ golang.org/x/sys v0.0.0-20190222072716-a9d3bda3a223 // indirect
+)
+
+go 1.19
gorelease
says:
# summary
Suggested version: v0.1.0
gocompat
says:
Your branch is up to date with 'origin/master'.
This PR is modifying both version.json
and non-markdown files.
The Release Checker is not able to analyse files that are not checked in to master
. This might cause the above analysis to be inaccurate.
Please consider performing all the code changes in a separate PR before cutting the release.
A draft GitHub Release has been created. It is going to be published when this PR is merged. You can modify its' body to include any release notes you wish to include with the release.
Thank you for submitting this PR! A maintainer will be here shortly to review it. We are super grateful, but we are also overloaded! Help us by making sure that:
The context for this PR is clear, with relevant discussion, decisions and stakeholders linked/mentioned.
Your contribution itself is clear (code comments, self-review for the rest) and in its best form. Follow the code contribution guidelines if they apply.
Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment. Next steps:
A maintainer will triage and assign priority to this PR, commenting on any missing things and potentially assigning a reviewer for high priority items.
The PR gets reviews, discussed and approvals as needed.
The PR is merged by maintainers when it has been approved and comments addressed.
We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution. We are very grateful for your contribution!