-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Semver #34
Comments
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
Hi @jmcarp - yes we can start semver tagging the package, it's something we have been meaning to do for awhile (thanks for the reminder!). I hope these are the last of the breaking changes for now. We do have a planned interface refactor planned, but we will be raising a PR for community review / feedback. |
@avade Any news on this? |
Bumps [github.com/cloudfoundry/socks5-proxy](https://github.com/cloudfoundry/socks5-proxy) from 3c6b4eec9c2d16c1dac4c42bdb5f755ba09daff8 to 0.2.0. This release includes the previously tagged commit. - [Release notes](https://github.com/cloudfoundry/socks5-proxy/releases) - [Commits](cloudfoundry/socks5-proxy@3c6b4ee...v0.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
There are breaking changes that have broker compile This reverts commit 0384d60.
I noticed that there have been a few minor breaking changes lately--would you all be open to using semantic versioning and tagging releases so that users can get a better sense of what's changing?
The text was updated successfully, but these errors were encountered: