aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authordiogo464 <[email protected]>2025-07-11 15:08:19 +0100
committerdiogo464 <[email protected]>2025-07-11 15:08:19 +0100
commitbfc3d24c1c3f0114d07e01afb38c840df046d1b8 (patch)
tree653574f6b738aa1ee7f9f1d794193e528e616951
parentf709604c54cea1fe830ae366ad246f9b0cd61d92 (diff)
chore: update Cargo.lock and add .claude directory
-rw-r--r--.claude/commands/release.md20
-rw-r--r--Cargo.lock2
2 files changed, 21 insertions, 1 deletions
diff --git a/.claude/commands/release.md b/.claude/commands/release.md
new file mode 100644
index 0000000..3a25e6e
--- /dev/null
+++ b/.claude/commands/release.md
@@ -0,0 +1,20 @@
1---
2name: release
3description: Create a new GitHub release by tagging and pushing
4---
5
6Create a new GitHub release for version {{version}}.
7
8Steps:
91. First check that we're on the main branch and that it's up to date
102. Update the version in Cargo.toml from its current value to {{version}} (without the 'v' prefix)
113. Commit the version change with message: "chore: bump version to {{version}}"
124. Create an annotated git tag with: git tag -a v{{version}} -m "Release v{{version}}"
135. Push the commits and tag to GitHub: git push origin main --follow-tags
14
15This will trigger the GitHub Actions workflow that automatically builds and releases the binaries.
16
17Important:
18- The version should be provided without the 'v' prefix (e.g., "1.0.0" not "v1.0.0")
19- Make sure all changes are committed before running this command
20- The GitHub Actions workflow will handle building binaries for all platforms and creating the release \ No newline at end of file
diff --git a/Cargo.lock b/Cargo.lock
index 92b55d7..994d010 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -403,7 +403,7 @@ dependencies = [
403 403
404[[package]] 404[[package]]
405name = "oar-p2p" 405name = "oar-p2p"
406version = "0.0.0" 406version = "0.2.0"
407dependencies = [ 407dependencies = [
408 "clap", 408 "clap",
409 "color-eyre", 409 "color-eyre",