StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html
Follow-up for #6220 to regenerate lockfiles/st2.lock and pull in the tooz update.
Along with that update, there were a variety of other packages updated, so I updated fixed-requirements.txt (and related files) to track the locked versions.
I reviewed the changelogs for all packages that had a major version bump, and we're not using the features that changed behavior.
Additional Changes
I also realized that we can remove lockfiles/setuptools.lock because it only has 2 deps in it (setuptools, wheel), both of which are explicitly required in lockfiles/st2.lock. So, I configured pants to use the st2 lockfile whenever it needs to do something like build wheels with setuptools.
I just found out about a pants feature that allows us to reduce duplication of the python interpreter constraints in pants.toml. Hopefully that will make it easier to grok where changes are required when we bump those constraints.
One of the virtualenv tests started failing, but I could not figure out which package triggered it. When I removed my virtualenv, and went back to master, the error message reverts to the old message for some time, and then consistently provides the new error message. So, I've experienced this same error on master without any of these upgrades. However, this is a minor error message that is only checked in a test, so I just updated the test to accept the new message as well.
Follow-up for #6220 to regenerate
lockfiles/st2.lock
and pull in the tooz update. Along with that update, there were a variety of other packages updated, so I updatedfixed-requirements.txt
(and related files) to track the locked versions.Here is a summary of the updates:
I reviewed the changelogs for all packages that had a major version bump, and we're not using the features that changed behavior.
Additional Changes
lockfiles/setuptools.lock
because it only has 2 deps in it (setuptools, wheel), both of which are explicitly required inlockfiles/st2.lock
. So, I configured pants to use thest2
lockfile whenever it needs to do something like build wheels with setuptools.pants.toml
. Hopefully that will make it easier to grok where changes are required when we bump those constraints.