in prep for the next release. I'm taking the opportunity to trim a dependency on error_chain. The error crate ecosystem is a moving target and preferred error crates change from year to year. This should be an application choice not a library choice. As such I'm going to prefer errors that only implement the std error interface because it is the standard error interface.
Closes: #xxx
How did you verify your change:
Unit tests and CI
What (if anything) would need to be called out in the CHANGELOG for the next release:
What did you implement:
in prep for the next release. I'm taking the opportunity to trim a dependency on error_chain. The error crate ecosystem is a moving target and preferred error crates change from year to year. This should be an application choice not a library choice. As such I'm going to prefer errors that only implement the std error interface because it is the standard error interface.
Closes: #xxx
How did you verify your change:
Unit tests and CI
What (if anything) would need to be called out in the CHANGELOG for the next release:
notes included