Skip to content

Releases: nemith/netconf

v0.0.2

06 Dec 16:11
b5fd09a
Compare
Choose a tag to compare

What's Changed

  • new session.Do API by @nemith in #60
  • allow more control of filtering Reply errors by @nemith in #61
  • build(deps): bump golang.org/x/crypto from 0.12.0 to 0.13.0 by @dependabot in #64
  • build(deps): bump golang.org/x/crypto from 0.13.0 to 0.15.0 by @dependabot in #66
  • build(deps): bump golang.org/x/crypto from 0.15.0 to 0.16.0 by @dependabot in #67
  • build(deps): bump golang.org/x/crypto from 0.16.0 to 0.17.0 by @dependabot in #68
  • build(deps): bump golang.org/x/crypto from 0.17.0 to 0.18.0 by @dependabot in #70
  • transport: fix infinate loop on chunkReader.Close() by @nemith in #71
  • build(deps): bump golang.org/x/crypto from 0.18.0 to 0.19.0 by @dependabot in #72
  • build(deps): bump golang.org/x/crypto from 0.19.0 to 0.21.0 by @dependabot in #75
  • build(deps): bump github.com/stretchr/testify from 1.8.4 to 1.9.0 by @dependabot in #74
  • bump for Go version 1.21 and 1.22 by @nemith in #76
  • build(deps): bump golang.org/x/crypto from 0.21.0 to 0.23.0 by @dependabot in #78
  • build(deps): bump golang.org/x/crypto from 0.23.0 to 0.24.0 by @dependabot in #79
  • build(deps): bump golang.org/x/crypto from 0.24.0 to 0.25.0 by @dependabot in #80
  • build(deps): bump golang.org/x/crypto from 0.25.0 to 0.27.0 by @dependabot in #82
  • build(deps): bump golang.org/x/crypto from 0.27.0 to 0.28.0 by @dependabot in #83
  • build(deps): bump golang.org/x/crypto from 0.28.0 to 0.29.0 by @dependabot in #86
  • bug fix in main receive loop by @ksproska in #85
  • build(deps): bump github.com/stretchr/testify from 1.9.0 to 1.10.0 by @dependabot in #87

New Contributors

Full Changelog: v0.0.1...v0.0.2

v0.0.1

28 Aug 22:23
2cc824f
Compare
Choose a tag to compare
v0.0.1 Pre-release
Pre-release

Initial release of the github.com/nemith/netconf package, a complete rewrite of the github.com/Juniper/go-netconf package (by the original author).

Note the API is not stable, however I will try to cut releases for breaking API changes in v0. Once the API has been stablized a 1.0 release will be cut and no breaking changes will be added (unless there is a v2 package).

This is being used in production and feedback is welcome.