Skip to content

build(deps): update module github.com/shopify/toxiproxy to v2.5.0

Jaime Martinez requested to merge build-deps-toxiproxy-2-5-0 into master

What does this MR do?

Updates toxiproxy to v2.5.0. We need a manual update instead of !1391 (comment 1514774499) as the package is now go.mod compatible, so it required a few more changes.

This MR contains the following updates:

Package Type Update Change
github.com/Shopify/toxiproxy require minor v2.1.4+incompatible -> v2.5.0

MR created with the help of gitlab-org/frontend/renovate-gitlab-bot

Release Notes

Shopify/toxiproxy

v2.5.0

Compare Source

Changes

New Contributors

Full Changelog: https://github.com/Shopify/toxiproxy/compare/v2.4.0...v2.5.0

Docker images

  • docker pull ghcr.io/shopify/toxiproxy:2.5.0

Homebrew

  • brew install shopify/shopify/toxiproxy

v2.4.0

Compare Source

Docker images

  • docker pull ghcr.io/shopify/toxiproxy:2.4.0

v2.3.0

Compare Source

Docker images

  • docker pull ghcr.io/shopify/toxiproxy:2.3.0

v2.2.0

Compare Source

  • Update linux packages to use /usr/bin folder as binary destination and change the executable names to exclude ARCH and OS names. New pathes: /usr/bin/toxiproxy-cli /usr/bin/toxiproxy-server (#​331, @​miry)
  • A new toxic to simulate TCP RESET (Connection reset by peer) on the connections by closing the stub Input immediately or after a timeout. (#​247 and #​333, @​chaosbox)

Docker images

  • docker pull ghcr.io/shopify/toxiproxy:2.2.0

v2.1.7

Compare Source

  • Set the valid version during the build process. Verify the correct verion of the built binaries with make release-dry (#​328, @​miry)

Docker images

  • docker pull ghcr.io/shopify/toxiproxy:2.1.7

v2.1.6

Compare Source

Docker images

  • docker pull ghcr.io/shopify/toxiproxy:2.1.6

v2.1.5

Compare Source

Changelog

Commits

eb81bfd Add Elixir Client to Readme f1070b0 Add Rust client link. 18165c8 Add example config.json file to README.md 653f495 Automate release with Github actions (#​302) 8029ed1 Create releases with goreleaser (#​301) 916f03a Fix typos d26384f Fixing dev.yml to allow running dev up 5321df3 Mention MacPorts in readme 8474b0e Merge branch 'master' into add_toxiproxy_elixir b0ba1c8 Merge pull request #​1 from Shopify/master 07d7b63 Merge pull request #​241 from Shopify/v2.1.4 10f0561 Merge pull request #​251 from nothinux/master 0ba0d2b Merge pull request #​253 from Shopify/updates cfe8289 Merge pull request #​260 from JesseEstum/example_config c262ed0 Merge pull request #​287 from Jcambass/add_toxiproxy_elixir 115744c Merge pull request #​293 from Shopify/feature/PA-Add-rust-client 335da76 Merge pull request #​294 from dnwe/dnwe/renovations 769a33c Merge pull request #​297 from Shopify/update-bundler-2.2.22-1 047ab7f Merge pull request #​298 from Shopify/dev-compat 9134ef6 Move to go modules 758c1e5 Release 2.1.5 (#​305) 0653399 Run tests for master and pull requests (#​303) 5e860e5 Support solaris platform (#​304) 517a128 Update build badge to Travis CI 9e1d709 Update bundler to 2.2.22 82715a0 Upgrade Golang and Ruby versions (#​299) febff58 chore: fix some minor govet/staticheck failures ad7d9e2 chore: gofmt -s -w f135051 chore: renovate dependencies 4ca1edd fix TOC in readme 5bb6b89 update docs

Docker images

  • docker pull ghcr.io/shopify/toxiproxy:2.1.5

Author checklist

  • Feature flags
    • Added feature flag:
    • This feature does not require a feature flag
  • I added unit tests or they are not required
  • I added documentation (or it's not required)
  • I followed code review guidelines
  • I followed Go Style guidelines
  • For database changes including schema migrations:
    • Manually run up and down migrations in a postgres.ai production database clone and post a screenshot of the result here.
    • If adding new queries, extract a query plan from postgres.ai and post the link here. If changing existing queries, also extract a query plan for the current version for comparison.
    • Do not include code that depends on the schema migrations in the same commit. Split the MR into two or more.
  • Ensured this change is safe to deploy to individual stages in the same environment (cny -> prod). State-related changes can be troublesome due to having parts of the fleet processing (possibly related) requests in different ways.

Reviewer checklist

  • Ensure the commit and MR tittle are still accurate.
  • If the change contains a breaking change, apply the breaking change label.
  • If the change is considered high risk, apply the label high-risk-change
  • Identify if the change can be rolled back safely. (note: all other reasons for not being able to rollback will be sufficiently captured by major version changes).

If the MR introduces database schema migrations:

  • Ensure the commit and MR tittle start with fix:, feat:, or perf: so that the change appears on the Changelog
If the changes cannot be rolled back follow these steps:
  • If not, apply the label cannot-rollback.
  • Add a section to the MR description that includes the following details:
    • The reasoning behind why a release containing the presented MR can not be rolled back (e.g. schema migrations or changes to the FS structure)
    • Detailed steps to revert/disable a feature introduced by the same change where a migration cannot be rolled back. (note: ideally MRs containing schema migrations should not contain feature changes.)
    • Ensure this MR does not add code that depends on these changes that cannot be rolled back.

Merge request reports