We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
patch
feat
fix
Checked → Update version, update repository, and release the library. Un-checked → Do nothing
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.
Update the following lines. Once merged, it will be reflected to changelogs/*.
changelogs/*.
models
algoliasearch
addUserAgent
version
To proceed this release, check the box below and close the issue. To skip this release, just close the issue.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Summary
Version Changes
patch
(e.g. v0.0.6)feat
orfix
commit, thus unchecked by default.patch
(e.g. v0.0.2)feat
orfix
commit, thus unchecked by default.patch
(e.g. v0.0.2)feat
orfix
commit, thus unchecked by default.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.
CHANGELOG
Update the following lines. Once merged, it will be reflected to
changelogs/*.
javascript
models
(feat(javascript): exposemodels
#252)algoliasearch
package (feat(javascript): providealgoliasearch
package #158)addUserAgent
method (feat(javascript): addaddUserAgent
method #154)version
variable (fix(javascript): prevent conflict withversion
variable #141)java
php
Approval
To proceed this release, check the box below and close the issue.
To skip this release, just close the issue.
The text was updated successfully, but these errors were encountered: