@involvex/super-agent-cli 0.0.84 → 0.0.85

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -1731,7 +1731,7 @@ var init_indexer = __esm(() => {
1731
1731
  var require_package = __commonJS((exports, module) => {
1732
1732
  module.exports = {
1733
1733
  name: "@involvex/super-agent-cli",
1734
- version: "0.0.84",
1734
+ version: "0.0.85",
1735
1735
  description: "An open-source AI agent that brings the power of Super Agent directly into your terminal.",
1736
1736
  keywords: [
1737
1737
  "cli",
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@involvex/super-agent-cli",
3
- "version": "0.0.84",
3
+ "version": "0.0.85",
4
4
  "description": "An open-source AI agent that brings the power of Super Agent directly into your terminal.",
5
5
  "keywords": [
6
6
  "cli",
@@ -13,8 +13,7 @@ if ($gitStatus) {
13
13
 
14
14
  # 2. Bump version, create commit and tag
15
15
  Write-Host "Bumping version and creating tag..."
16
- # `bun pm version patch` automatically creates a commit and a tag like vX.Y.Z
17
- # We need to capture the new version string.
16
+ # `bun pm version patch` automatically updates package.json and bun.lockb, then creates a commit and a tag like vX.Y.Z
18
17
  $newVersionOutput = bun pm version patch
19
18
  $NEW_VERSION = ($newVersionOutput | Select-Object -Last 1).Trim() # Assumes the last line is the version, e.g., "v1.0.1"
20
19
  Write-Host "Version bumped to $NEW_VERSION"
@@ -23,21 +22,28 @@ Write-Host "Version bumped to $NEW_VERSION"
23
22
  Write-Host "Generating CHANGELOG.md..."
24
23
  bun run changelog
25
24
 
26
- # 4. Stage CHANGELOG.md
27
- Write-Host "Staging CHANGELOG.md..."
28
- git add CHANGELOG.md
25
+ # 4. Run format and lint:fix to ensure all files (including package.json and CHANGELOG.md) adhere to standards
26
+ # This step might modify package.json and CHANGELOG.md again if they were not perfectly formatted
27
+ Write-Host "Running format and lint fix to ensure consistency..."
28
+ bun run format # Reformats files, including package.json and CHANGELOG.md if needed
29
+ bun run lint:fix # Fixes linting issues, could touch files again
29
30
 
30
- # 5. Amend the previous commit to include CHANGELOG.md
31
- # git commit --amend automatically takes the last commit message if --no-edit is used
32
- Write-Host "Amending previous commit to include CHANGELOG.md..."
31
+ # 5. Stage all changes that occurred since the last commit (which was the version bump)
32
+ # This includes CHANGELOG.md and any reformatting applied to package.json (or other files touched by format/lint)
33
+ Write-Host "Staging all remaining changes (CHANGELOG.md and formatting updates)..."
34
+ git add . # Use 'git add .' to stage all modifications
35
+
36
+ # 6. Amend the previous commit (the version bump commit) to include these new staged changes
37
+ # git commit --amend --no-edit keeps the existing commit message (e.g., "vX.Y.Z")
38
+ Write-Host "Amending previous commit to include CHANGELOG.md and formatting changes..."
33
39
  git commit --amend --no-edit
34
40
 
35
- # 6. Force update the tag to point to the amended commit (important!)
41
+ # 7. Force update the tag to point to the amended commit (important!)
36
42
  # `git commit --amend` creates a new commit SHA. We need to update the tag to point to this new SHA.
37
43
  Write-Host "Updating Git tag $NEW_VERSION to new commit SHA..."
38
44
  git tag -f $NEW_VERSION HEAD
39
45
 
40
- # 7. Run the project build (dist/ is ignored, so it's not committed)
46
+ # 8. Run the project build (dist/ is ignored, so it's not committed)
41
47
  Write-Host "Running project build..."
42
48
  bun run build
43
49