Skip to content

Commit 5776b2e

Browse files
authored
Merge pull request #69 from semi-technologies/WEAVIATE-119
JS client npm package hasn't been updated in a year
2 parents 4746310 + 60df879 commit 5776b2e

File tree

5 files changed

+138
-3
lines changed

5 files changed

+138
-3
lines changed

CODE_OF_CONDUCT.md

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to make participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies within all project spaces, and it also applies when
49+
an individual is representing the project or its community in public spaces.
50+
Examples of representing a project or community include using an official
51+
project e-mail address, posting via an official social media account, or acting
52+
as an appointed representative at an online or offline event. Representation of
53+
a project may be further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at laura@semi.technology. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

CONTRIBUTE.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
### Thanks for looking into contributing to Weaviate JavaScript client!
2+
Contributing works pretty easy. You can do a pull request or you can commit if you are part of a Weaviate team.
3+
4+
### Code of Conduct
5+
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
6+
[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-v2.0%20adopted-ff69b4.svg)](CODE_OF_CONDUCT.md)
7+
8+
9+
### How we use Gitflow
10+
How we use [Gitflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) and how you can contribute following a few steps.
11+
12+
- The master branch is what is released and developed currently.
13+
- You can create a feature-branch that is named: feature/YOUR-FEATURE-NAME.
14+
- Your feature branch always has the master branch as a starting point.
15+
- When you are done with your feature you should create a pull request into the master branch.
16+
- The master branch is protected.
17+
18+
### Tagging your commit
19+
20+
Always add a reference to your issue to your git commit.
21+
22+
For example: `gh-100: This is the commit message`
23+
24+
AKA: smart commits
25+
26+
### Pull Request
27+
28+
If you create a pull request without smart commits, the pull request will be [squashed into](https://blog.github.com/2016-04-01-squash-your-commits/) one git commit.
29+
30+
### Contributor License Agreement
31+
32+
Contributions to Weaviate JavaScript client must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of Weaviate JavaScript client. Go to [this page](https://www.semi.technology/playbooks/misc/contributor-license-agreement.html) to read the current agreement.
33+
34+
The process works as follows:
35+
36+
- You contribute by opening a [pull request](#pull-request).
37+
- If your account has no CLA, a DocuSign link will be added as a comment to the pull request.

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ A javascript client for easy interaction with a weaviate instance.
99
## Support
1010

1111
- [Stackoverflow for questions](https://stackoverflow.com/questions/tagged/weaviate).
12-
- [Github for issues](https://github.com/semi-technologies/weaviate-python-client/issues).
12+
- [Github for issues](https://github.com/semi-technologies/weaviate-javascript-client/issues).
1313

1414
## Contributing
1515

16-
- [How to Contribute](https://github.com/semi-technologies/weaviate/blob/master/CONTRIBUTE.md).
16+
- [How to Contribute](https://github.com/semi-technologies/weaviate-javascript-client/blob/master/CONTRIBUTE.md).
1717

1818
## Build Status
1919

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "weaviate-client",
3-
"version": "2.3.0",
3+
"version": "2.10.0",
44
"description": "Javascript client for Weaviate",
55
"main": "lib.js",
66
"scripts": {

tools/prepare_release.sh

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
#!/bin/bash
2+
3+
set -euo pipefail
4+
5+
VERSION="$(jq -r '.version' ./package.json)"
6+
REQUIRED_TOOLS="jq git"
7+
8+
for tool in $REQUIRED_TOOLS; do
9+
if ! hash "$tool" 2>/dev/null; then
10+
echo "This script requires '$tool', but it is not installed."
11+
exit 1
12+
fi
13+
done
14+
15+
if git rev-parse "v$VERSION" >/dev/null 2>&1; then
16+
echo "Cannot prepare release, a release for v$VERSION already exists"
17+
exit 1
18+
fi
19+
20+
git commit -a -m "prepare release v$VERSION"
21+
22+
git tag -a "v$VERSION" -m "$VERSION"

0 commit comments

Comments
 (0)