[BUG] OpenApi at version '1.0.0' on 1.x branch vs '1.0.1' for other gems

[woidda]

Not really a bug, but a tiny annoyance when you update your gems.

Should OpenSearch::API::VERSION not be '1.0.1' or don't you keep the different gems in sync for the published versions?

See:

.../1.x/opensearch-api/lib/opensearch/api/version.rb

vs

.../1.x/opensearch-transport/lib/opensearch/transport/version.rb

[dblock]

Related, we're trying to centralize API spec and publish OpenAPI in opensearch-project/opensearch-api-specification#34.

[nhtruong]

Hi @woidda,
We're not syncing up the versions of these gems. The fact that the versions appeared in sync was a coincidence as we used to do releases for these gems at the same time. We're now able to do releases much more often, and we're planning to deploy a new version of each gem as soon as it's viable.

If you install the opensearch-ruby or opensearch-aws-sigv4 gem, the appropriate versions of api and transport gems will be installed as dependencies.

[woidda]

I use these two:

gem "opensearch-ruby", "~>1.0"
gem "opensearch-transport", "~>1.0"

So I can replace this by including only opensearch-ruby, correct?

OK this makes it easier. I was not sure about the semantics you use for versioning as the elasticsearch gems afaik used the same version numbers for fitting parts.

Thanks for your reply and your work. I am looking forward to when opensearch becomes more mainstream and the confusion around naming things and what libs are available in what programming language disappears...

[nhtruong]

@woidda Thanks for the kind words and for understanding. And yes we have plans to improve these clients, esp in regard to Opensearch's unique features :)