✨ Source Facebook Pages: Upgrade Facebook API to v19.0

[airt]

What

• Resolve Source Facebook Pages: migrate API to v19.0 #25515

How

• Upgrade Facebook API to v19.0

Recommended reading order

1. airbyte-integrations/connectors/source-facebook-pages/source_facebook_pages/manifest.yaml

User Impact

1. Invalid field removed: messenger_ads_default_page_welcome_message

Pre-merge Actions

Expand the relevant checklist and delete the others.

Updating a connector

Community member or Airbyter

• Grant edit access to maintainers (instructions)
• Unit & integration tests added

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

• Create a non-forked branch based on this PR and test the below items on it
• Build is successful
• If new credentials are required for use in CI, add them to GSM. Instructions.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 20, 2024 7:35am

[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.

[marcosmarxm]

Thanks for the contribution @airt I requested to the connector team to review it.

[marcosmarxm]

Solved by #35746 sorry the lack of update here @airt

[airt]

Solved by #35746 sorry the lack of update here @airt

@marcosmarxm Seems that #35746 is for Marketing and this one is for Pages, they are not the same source 😂

[marcosmarxm]

lol!!!! my baddd @airt

[midavadim]

I close this PR since API version was updated in another PR:
#36015