chore: release 2022-03-30

[eunjae-lee]

Summary

Version Changes

• javascript: v0.0.5 -> minor (e.g. v0.1.0)
• java: v0.0.1 -> minor (e.g. v0.1.0)
• php: v0.0.1 (no commit)

Checked → Update version, update repository, and release the library.
Un-checked → Do nothing

The JavaScript repository consists of several packages with independent versioning. Release type is applied to each version.

For example, if the release type is `patch`,

* algoliasearch@5.0.0 -> 5.0.1
* @algolia/client-search@5.0.0 -> 5.0.1
* @algolia/client-abtesting@5.0.0 -> 5.0.1
* ...
* @algolia/client-predict@0.0.1 -> 0.0.2
* ...
* @algolia/requester-browser-xhr@0.0.5 -> 0.0.6.

CHANGELOG

Update the following lines. Once merged, it will be reflected to changelogs/*.

javascript

• 09259f7 feat(javascript): expose requestOptions and cache options (feat(javascript): expose requestOptions and cache options #283)
• 272ebd3 feat(javascript): use responses and requests cache (feat(javascript): use responses and requests cache #281)
• 2e7f208 feat(javascript): add cache layer (feat(javascript): add cache layer #274)

java

• e4a064f feat(java): retry strategy APIC-261 (feat(java): retry strategy APIC-261 #286)
• f51984f fix(java): escape oneOf naming (fix(java): escape oneOf naming #268)

Approval

To proceed this release, check the box below and close the issue.
To skip this release, just close the issue.

• Approved

[shortcuts]

Will our first working release only contains this few commits? Or do you know if it's possible to start from the root of this repository?

[eunjae-lee]

@shortcuts Actually I put released tag somewhere in the recent commit (probably right after your 0.0.4 release). It's all about versioning + changelog. I can tag a very old commit as released, but it won't mean much. It's because, for our first public stable release, we will put some stable versions like 5.0.0, and we need to write changelogs by hand, because we don't want to list all the history of our work.