🐛 source-stripe: Temporarily pin stripe connector to 5.1.3

[girarda]

What

• Pin stripe to 5.1.3
• I used destination-mysql-strict-encrypt as a model for how to pin the version both on cloud and oss

How

• Set dockerImageTag to the cloud and oss registries

An alternative would be to release the connector with the previous version of the CDK.

Recommended reading order

1. airbyte-integrations/connectors/source-stripe/metadata.yaml

🚨 User Impact 🚨

Cloud users will use 5.1.3
New OSS deploys will use 5.1.3. Existing ones won't be automatically updated.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
airbyte-docs	⬜️ Ignored (Inspect)		Jan 22, 2024 8:13pm

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[maxi297]

Do we still need this @girarda given the fix 5.2.1 is in prod?

[girarda]

closing because this is not necessary anymore