Hub SSOT - Do we want to support package + metadata versioning?

[MeltyBot]

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/223

Originally created by @pnadolny13 on 2022-03-24 14:17:25

---

First proposed in https://gitlab.com/meltano/hub/-/issues/180.

If we allow users to pin a version of their package, they need to be able to pin the metadata at that point in time too as metadata changes with the code. If a user has a 0.9.0 package version installed and a breaking change (say a new required setting was added) was introduced to the 1.0.0 (latest) version along with metadata updates, they cant just pull the latest metadata or their pipeline will break.

This may be resolved by the lock mechanism https://gitlab.com/meltano/meltano/-/issues/3031 but we should decide if we only want to the hub to represent the "latest" or "current" metadata.

This decision affects the way we implement the V2 API and the organization of the files in the hub.

[MeltyBot]

View 11 previous comments from the original issue on GitLab

[tayloramurphy]

Notes from chat with AJ:

• supported Meltano versions: meltano-version: ~2.5.0
• Columns: date changed, meltano version constraints, comment of update type

Figure out how to automate on Hub, then figure out how Meltano can resolve it.