some like stripe I am 100% confident I was on latest version before this upgrade

Interesting that stripe is affected, since it has not had a new version since the end of July.

@Jeff Crooks, what was the previous Airbyte version you were running before the upgrade?

Also do you remember which version stripe rolled back to after the upgrade?

I believe I was on .13

stripe was back 2 version, .14 vs .16

and yes I was confused... I said oh hell yeah look at all these updates! wait a second... 🙂

Thank you. This is very useful.

Hmm, I cannot reproduce this issue. I launched 0.29.13, and then upgraded it to 0.29.15, and don’t see any roll back. On contrary, all connectors are automatically upgraded to the latest version packaged with 0.29.15 as expected. Theoretically 0.29.15 should only see the latest version of stripe, and won’t be able to roll it back. Let me think more about this.

no worries, was easy to get back updated

i did have a failed attempt to .14 last week that I had to rollback, may be related

its rare for any breaking changes, so when something happens i like to post in feedback in case others are seeing it

Right, sorry about the .14 issue. There was a bug introduced in that version.

all good i still love yall 🙂

Thank you~~

The rolling back to .14 part is new. I will try that.

@Liren Tu upgrading to .17 just did the same thing

You are not using Stripe in any sync, right? I will add more logging in the server to help debug this issue.

I created an issue to track this: https://github.com/airbytehq/airbyte/issues/5954

Stripe is my #1 sync at the moment 🙂

Hmm, that’s really strange. When you upgrade Airbyte, any connectors that are in use won’t be changed at all. https://github.com/airbytehq/airbyte/blob/master/airbyte-config/persistence/src/ma[…]va/io/airbyte/config/persistence/DatabaseConfigPersistence.java Since Stripe is in use, theoretically it should always remain the same.

its definitely changed on both upgrades ive done in the last 2 days

Just to double check, Jeff, do you export your configs before each upgrade, and import them back later on?

I do not, should I be?

I thought once auto migration rolled out, this happens as part of the upgrade

No, you don’t need to. If you do that regularly, that could explain the roll back. I was just trying to rule that possibility out.

@Liren Tu, same behavior moving to .19

different connectors though, this time the stripe one didnt rollback

@Jeff Crooks, yes, I have located the root cause of this bug last night. Working on a fix now. Target to create a new release today.

@Jeff Crooks, the fix has been released in

v0.29.21-alpha

. https://github.com/airbytehq/airbyte/releases/tag/v0.29.21-alpha

no issues on upgrade. still facing the issue where i dont see the updated mongo connector, but I believe that issue is still open on github