According to your experience how likely is that switching from dagster version 1.2.1 to 1.2.6 will break your code? Reformulated: what is your experience, how strictly dagster follows the semantic versioning?

In case you’re not using experimental or deprecated features (which would trigger a warning) you really don’t have to worry. I’ve been using Dagster since roughly 0.14.x and try to keep the packages updated as much as I can, can’t recall of a single instance where an upgrade broke something.

Thanks @Vinnie thanks ( ... and you are right in the current code base I am not using experimental features)

Overall it's been ok but I did come across an issue that prevented us from upgrading dagster_k8s in 1.2.6 https://dagster.slack.com/archives/C01U5LFUZJS/p1680824572154439

Hi Peter. We have a policy of only releasing breaking changes at major releases i.e.

1.3.0

,

1.4.0

, etc. The dot releases in the middle should not result in any breakages. Sometimes accidental issues come up (like k8s one above) but if you report it we'll try our best to fix it for you in the future releases.

@Peter Fulop also want to state, i've been very impressed with the dedication of the dagster team. The minor bug i mentioned in the last release was already addressed. Kudos to @daniel for the responsiveness with this and other issues