Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
55 changes: 55 additions & 0 deletions RELEASE_EXECUTION_SUMMARY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
# Release Script Execution Summary

## Executed: `scripts/release`

### Date
2026-02-01

### Action Taken
The release script was successfully executed, which performed the following operations:

1. **Fetched latest tags** from the remote repository
2. **Identified latest version**: `v3.17.38`
3. **Calculated new version**: `v3.17.39` (patch increment)
4. **Created new tag locally**: `v3.17.39`

### Tag Details
- **Tag Name**: `v3.17.39`
- **Commit**: `05ffdd7e447f3f1e6f7089645d5be9e1b1168374`
- **Branch**: `copilot/run-release-script`

### What Happens Next

The tag `v3.17.39` has been created locally. When this tag is pushed to the remote repository, it will trigger the GitHub Actions workflow defined in `.github/workflows/release.yml`, which will:

1. Build the Go binaries using GoReleaser
2. Build platform Docker images
3. Publish packages to NPM
4. Create a GitHub release

### How to Complete the Release

To complete the release and trigger the automated release workflow, the tag needs to be pushed to GitHub:

```bash
git push origin v3.17.39
```

Alternatively, the tag will be pushed when this PR branch is merged and the release process is run again on the main branch.

### Release Script Options

The release script supports the following options:

- **Default** (no flags): Increments the patch version (e.g., 3.17.38 → 3.17.39)
- **`--minor` flag**: Increments the minor version and resets patch to 0 (e.g., 3.17.38 → 3.18.0)

### Example Usage

```bash
# Create a patch release (3.17.39 → 3.17.40)
./scripts/release

# Create a minor release (3.17.39 → 3.18.0)
./scripts/release --minor
```