-
Notifications
You must be signed in to change notification settings - Fork 5
Expand file tree
/
Copy pathMakefile
More file actions
37 lines (27 loc) · 1.1 KB
/
Makefile
File metadata and controls
37 lines (27 loc) · 1.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
# add a new dependency with `uv add <package>`.
# This will add it to the pyproject.toml file and the uv.lock file
# `uv tool run` is equivalent to `uvx`
# by default `uvx` will run the command with the same name as the package when run like `uvx <package>`.
# when run like `uv tool run . <package>` it should do the same as previous command, but locally.
run-dev:
uv tool run . sherlock-mcp
# When a new version is not found, you can refresh the package with: uvx --refresh sherlock-mcp@0.1.1
run:
uvx --refresh sherlock-mcp
# In order to release a new version, you need to:
# 0. Clean previous releases
clean:
rm -rf dist
# 1. Update the version in the pyproject.toml file
# 2. Sync this new package version into the pyproject.toml with:
sync-version:
uv sync
# 3. Build the package
build: clean
uv build
# 4. Test the release locally using the release wheel. I am not sure why the command `sherlock-mcp` can't be ommited here.
run-release: build
uv tool run --with dist/sherlock_mcp-0.1.1-py3-none-any.whl sherlock-mcp
# 5. Release the package to PyPI
release: build
uv publish --token $(PYPI_TOKEN)